| 2 |
Approval of Agenda |
|
| R1-2400000 |
Draft Agenda of RAN1#116 meeting |
RAN1 Chair |
| R1-2400003 |
RAN1#116 Meeting Management, Timelines, Scope, Process |
ETSI MCC |
| 3 |
Highlights from RAN plenary |
|
| R1-2400001 |
Highlights from RAN#102 |
RAN1 Chair |
| 4 |
Approval of Minutes from previous meetings |
|
| R1-2400002 |
Report of RAN1#115 meeting |
ETSI MCC |
| 5 |
Incoming Liaison Statements |
|
| R1-2400004 |
LS on Sidelink CSI Reporting MAC-CE for SL-CA |
RAN2, OPPO |
| R1-2400005 |
LS on Rel-18 RAN2 TP for TR 37.985 |
RAN2, Huawei |
| R1-2400006 |
LS to RAN1 on RAN2 addition to NTN Self Evaluation |
RAN2, Ericsson |
| R1-2400007 |
LS on UL Tx Switching |
RAN2, Huawei |
| R1-2400008 |
LS on MAC agreements for SL positioning |
RAN2, Huawei |
| R1-2400009 |
LS on RAN2 agreements for satellite switch with resync |
RAN2, Apple |
| R1-2400010 |
Reply LS on frequencyInfo for NR SL RSRP measurements |
RAN2, Huawei |
| R1-2400011 |
LS on introduction of RAT-Dependent integrity |
RAN2, CATT |
| R1-2400012 |
Reply LS to RAN4 on BWP operation without restriction |
RAN2, vivo |
| R1-2400013 |
Response LS on PEMAX,CA for SL CA |
RAN2, LG Electronics |
| R1-2400014 |
Reply LS on network assistant signalling for advanced receivers |
RAN2, CATT, China Telecom |
| R1-2400015 |
Reply to LS on AI/ML Core Network enhancements |
RAN3, ZTE |
| R1-2400016 |
LS on LMF involvement in SL-PRS resource allocation |
RAN3, xiaomi |
| R1-2400017 |
LS on OAM requirements for UE location verification |
RAN3, CATT |
| R1-2400018 |
Reply LS on TA validation for LPHAP |
RAN4, Huawei |
| R1-2400019 |
LS on SL-U RSSI measurement |
RAN4, Nokia |
| R1-2400020 |
Reply LS on measurement definitions for positioning with bandwidth aggregation |
RAN4, Huawei |
| R1-2400021 |
LS on Layer-1/2/3 ATG UE features and koffset mechanism |
RAN4, CMCC |
| R1-2400022 |
LS Reply on coherence between PUSCH and 8-ports SRS with partial dropping |
RAN4, Qualcomm Incorporated |
| R1-2400023 |
Reply LS on guard period for SRS and PRS bandwidth aggregation for positioning |
RAN4, CATT |
| R1-2400024 |
Reply LS on PSFCH power control |
RAN4, Huawei |
| R1-2400025 |
LS on UE capabilities for MPR reduction |
RAN4, Nokia |
| R1-2400026 |
LS on NTN VSAT capability |
RAN4, ZTE |
| R1-2400027 |
LS on UE capability to support DMRS bundling for GSO and NGSO |
RAN4, Ericsson |
| R1-2400028 |
Reply LS on L1 measurements for LTM |
RAN4, Ericsson |
| R1-2400029 |
LS on n-TimingAdvanceOffset for PDCCH order RACH |
RAN4, Huawei |
| R1-2400030 |
Response to reply LS on SRS and PRS bandwidth aggregation for positioning |
RAN4, Ericsson |
| R1-2400031 |
LS on RAN4 UE feature list for Rel-18 |
RAN4, CMCC |
| R1-2400032 |
LS on RAN4 UE feature list for Rel-18 (version 2) |
RAN4, CMCC |
| R1-2400033 |
LS on Rel-18 Tx switching enhancement |
RAN4, Huawei |
| R1-2400034 |
LS reply on further clarifications on enhancements to realize increasing UE power high limit for CA and DC |
RAN4, Huawei |
| R1-2400035 |
LS on the progress update of AI/ML Management specifications in SA5 |
SA5, NEC, Intel |
| R1-2400140 |
Discussion on RAN2 LS on MAC agreement for SL positioning |
Huawei, HiSilicon |
| R1-2400141 |
Discussion on measurement definitions for positioning with bandwidth aggregation |
Huawei, HiSilicon |
| R1-2400152 |
Discussion on R18 UL Tx switching |
Huawei, HiSilicon |
| R1-2400170 |
Discussion on LS on RAN2 agreements for satellite switch with resync |
Spreadtrum Communications |
| R1-2400184 |
LS reply on introduction of RAT-Dependent integrity |
SA2, CATT |
| R1-2400212 |
Draft reply LS on MAC agreements for SL positioning |
vivo |
| R1-2400213 |
Discussion on LS on measurement definitions for positioning with bandwidth aggregation |
vivo |
| R1-2400214 |
Discussions on RAN2 LS on RACH-less Handover |
vivo |
| R1-2400215 |
Discussions on RAN2 LS for satellite switch with resync |
vivo |
| R1-2400282 |
Reply LS to RAN4 on n-TimingAdvanceOffset for PDCCH order RACH |
ZTE |
| R1-2400306 |
Discussion on RAN 2 LS on MAC agreements for SL positioning |
CMCC |
| R1-2400307 |
Discussion on RAN4 LS on Layer-1/2/3 ATG UE features and koffset mechanism |
CMCC |
| R1-2400308 |
Discussion on RAN2 LS on the agreements for satellite switch with re-sync |
CMCC |
| R1-2400349 |
Further discussion on LS on the system parameters for NTN above 10 GHz |
ZTE |
| R1-2400350 |
Further discussion on RAN2 LS on RACH-less Handover |
ZTE |
| R1-2400404 |
Discussion on FR2 issues for Rel-18 NTN |
CATT |
| R1-2400450 |
Discussion on reply LS to SA5 on AI/ML Management specifications in SA5 |
CATT |
| R1-2400454 |
Discussion on MAC agreements for SL positioning |
CATT |
| R1-2400455 |
Draft reply LS on MAC agreements for SL positioning |
CATT |
| R1-2400456 |
Draft reply LS on Sidelink CSI Reporting MAC-CE for SL-CA |
CATT, CICTCI |
| R1-2400500 |
Draft reply LS on UL Tx switching |
ZTE |
| R1-2400583 |
Discussion and TP on SL RSSI measurement in SL-U |
OPPO |
| R1-2400589 |
Discussion on LS for satellite switch with resync |
OPPO |
| R1-2400637 |
Discussion on the LS from RAN4 on SL-U RSSI measurement |
ZTE, Sanechips |
| R1-2400678 |
LS on new definitions of energy efficiency and energy consumption |
SA5, Huawei |
| R1-2400697 |
Discussion on RAN2 LS on RACH-less handover |
Samsung |
| R1-2400698 |
Discussion on reply LS on MAC agreements for SL positioning |
Samsung |
| R1-2400785 |
Discussion on LS on SL-U RSSI measurement |
LG Electronics |
| R1-2400816 |
Considerations on the system parameters for FR2-NTN |
THALES |
| R1-2400891 |
Draft LS reply on the progress update of AI/ML Management specifications in SA5 |
NEC |
| R1-2400930 |
Draft reply LS on Sidelink CSI Reporting MAC-CE for SL-CA |
TOYOTA InfoTechnology Center |
| R1-2400967 |
Draft Reply LS on MAC agreements on SL positioning |
Intel Corporation |
| R1-2400968 |
Further discussion on NR over NTN operation in bands defined by FR2-NTN |
Nokia, Nokia Shanghai Bell |
| R1-2400969 |
Considerations for satellite switch with resync for NR over NTN |
Nokia, Nokia Shanghai Bell |
| R1-2400975 |
Discussion on RAN4 LS on the system parameters for NTN above 10 GHz |
Ericsson |
| R1-2400978 |
Discussion on RAN4 LS on UE capability to support DMRS bundling for GSO and NGSO |
Ericsson |
| R1-2400980 |
Discussion of RAN4 LS on the system parameters for NTN above 10 GHz |
Apple |
| R1-2400981 |
Discussion on RAN2 LS on RACH-less Handover |
Apple |
| R1-2400982 |
Discussion on RAN2 LS on Satellite Switch with Resync |
Apple |
| R1-2400983 |
Draft Reply LS on Satellite Switch with Resync |
Apple |
| R1-2400984 |
Discussion on RAN4 LS on Layer-1/2/3 ATG UE Features and Koffset Mechanism |
Apple |
| R1-2400985 |
Discussion on RAN4 LS on SL-U RSSI Measurement |
Apple |
| R1-2400986 |
Draft Reply on RAN4 LS on SL-U RSSI Measurement |
Apple |
| R1-2401068 |
Draft reply LS on MAC agreements for SL positioning |
ZTE |
| R1-2401069 |
Draft reply LS on LMF involvement in SL PRS resource allocation |
ZTE |
| R1-2401087 |
Discussion on RAN2 LS on UL Tx switching |
NTT DOCOMO, INC. |
| R1-2401163 |
Discussions on RAN4 LS on FR2-NTN aspects |
Sharp |
| R1-2401164 |
Discussions on RAN4 LS on SL-U RSSI measurement |
Sharp |
| R1-2401203 |
Draft LS reply on the progress update of AI/ML Management specifications in SA5 |
Nokia, Nokia Shanghai Bell |
| R1-2401262 |
Discussion on LS on RAN2 agreements for satellite switch with resync |
Ericsson |
| R1-2401341 |
Discussion on RAN2 LS on RACH-less handover |
Ericsson |
| R1-2401353 |
Discussion on Reply LS on measurement definitions for positioning with bandwidth aggregation |
Ericsson |
| R1-2401354 |
Discussion on RAN2 LS on Sidelink CSI Reporting MAC-CE for SL-CA |
Nokia, Nokia Shanghai Bell |
| R1-2401368 |
Discussion of RAN4 LS on UE capabilities for MPR reduction |
Ericsson |
| R1-2401375 |
Discussion on RAN4 LS on SL-U RSSI measurement |
Huawei, HiSilicon |
| R1-2401376 |
Discussion on RAN2 LS on Sidelink CSI Reporting MAC-CE for SL-CA |
Huawei, HiSilicon |
| R1-2401378 |
Further discussion on LS for RACH-less handover |
Huawei, HiSilicon |
| R1-2401379 |
Discussion on RAN1 impact to support the RAN4 work on NTN above 10GHz |
Huawei, HiSilicon |
| R1-2401381 |
Draft reply LS on MAC agreement for SL positioning |
Huawei, HiSilicon |
| R1-2401382 |
Draft reply LS on measurement definitions for positioning with bandwidth aggregation |
Huawei, HiSilicon |
| R1-2401387 |
Draft reply LS on UL Tx switching |
Huawei, HiSilicon |
| R1-2401392 |
Discussion on the reply LS on RAN2 agreements for satellite switch with resync |
Huawei, HiSilicon |
| R1-2401406 |
Draft Reply to LS on Sidelink CSI Reporting MAC-CE for SL-CA |
Qualcomm Incorporated |
| R1-2401463 |
Discussion on Reply LS on coherence between PUSCH and 8-ports SRS with partial dropping |
Ericsson |
| R1-2401679 |
LS on questions and recommendations to Rel-18 RAN1 UE features list |
RAN2, Intel |
| 7.1 |
Maintenance on NR Releases 15 – 16 |
|
| R1-2400268 |
Discussion on SRS transmission occasion |
vivo |
| R1-2400283 |
Discussion on SCell Type 1 virtual PHR reporting in UL CA |
ZTE |
| R1-2400286 |
Discussion on several ambiguities with type 2 CG PUSCH |
ZTE |
| R1-2400387 |
Draft CR on Rate Matching for PUSCH |
Google |
| R1-2400388 |
Draft CR on SRS power scaling |
Google |
| R1-2400389 |
Discussion on SRS power scaling |
Google |
| R1-2400520 |
Discussion on issues with type 2 CG-PUSCH |
Ericsson |
| R1-2400577 |
Discussion on SRS transmission occasion and power scaling |
OPPO |
| R1-2400682 |
Continuation discussion on clarifications on SUL |
Nokia, Nokia Shanghai Bell |
| R1-2400699 |
Discussion on aperiodic triggering for SRS carrier switching |
Samsung |
| R1-2400700 |
Discussion on SRS transmission occasion |
Samsung |
| R1-2400701 |
Discussion on the timeline issue for UCI multiplexing during HARQ-ACK overriding procedure |
Samsung |
| R1-2400702 |
Correction on timeline requirement for UCI multiplexing |
Samsung |
| R1-2400703 |
Correction on UCI multiplexing in a PUSCH transmission |
Samsung |
| R1-2400943 |
On SCell Type 1 virtual PHR reporting in UL CA |
Nokia, Nokia Shanghai Bell |
| R1-2400944 |
Clarification on SCell Type 1 virtual PHR reporting in UL CA |
Nokia, Nokia Shanghai Bell |
| R1-2400945 |
On aperiodic triggering support for SRS carrier switching |
Nokia, Nokia Shanghai Bell |
| R1-2400946 |
Remaining CG PUSCH type2 issues |
Nokia, Nokia Shanghai Bell |
| R1-2400947 |
On UCI dropping procedure for UCI-on-PUSCH |
Nokia, Nokia Shanghai Bell |
| R1-2400948 |
Clarification to multi-CSI-PUCCH-ResourceList |
Nokia, Nokia Shanghai Bell |
| R1-2400949 |
Discussion on modifying TBS limitation for reserved MCS retransmissions |
Nokia, Nokia Shanghai Bell |
| R1-2400950 |
Clarification on not multiplexing UCI on MSG3 PUSCH |
Nokia, Nokia Shanghai Bell, CATT, Ericsson |
| R1-2400951 |
ssb-index-RSRP CSI report dropping due to absence of CSI-RS |
Nokia, Nokia Shanghai Bell |
| R1-2400987 |
Remaining ambiguity issues on the 1st Type-2 CG PUSCH |
Apple |
| R1-2401075 |
Aperiodic SRS Carrier Switching |
Ericsson |
| R1-2401181 |
Correction on maximum number of PDCCH candidates determination for CSS |
Beijing Xiaomi Software Tech |
| R1-2401284 |
Clarifying ambiguities with type 2 CG-PUSCH |
MediaTek Inc. |
| R1-2401285 |
On common PUCCH/PUSCH configuration and SUL |
MediaTek Inc. |
| R1-2401286 |
[R16] Draft 38.212 CR on common PUCCH/PUSCH configuration and SUL |
MediaTek Inc. |
| R1-2401287 |
[R17] Draft 38.212 CR on common PUCCH/PUSCH configuration and SUL |
MediaTek Inc. |
| R1-2401288 |
[R18] Draft 38.212 CR on common PUCCH/PUSCH configuration and SUL |
MediaTek Inc. |
| R1-2401369 |
SRS Tx occasion and power scaling |
Ericsson |
| R1-2401370 |
Draft CR on multi-resource SRS port power scaling |
Ericsson |
| R1-2401371 |
Draft CR on simultaneous SRS resource transmission |
Ericsson |
| R1-2401383 |
Clarifications relating to type 2 CG-PUSCH |
Huawei, HiSilicon |
| R1-2401384 |
Discussion on TBS limitation for HARQ retransmissions with reserved MCS |
Huawei, HiSilicon |
| R1-2401388 |
Discussion on uplink carrier determination for SUL without UE dedicated configuration |
Huawei, HiSilicon |
| R1-2401389 |
Discussion on power control parameters for PHR of SCell |
Huawei, HiSilicon |
| R1-2401390 |
Discussion on SRS carrier switching triggered by multiple DCIs |
Huawei, HiSilicon |
| R1-2401393 |
Correction on SRI for DCI format 0_2 in TS 38.212 |
Huawei, HiSilicon |
| R1-2401394 |
Discussion on mapping order of CSI report |
Huawei, HiSilicon |
| R1-2401395 |
Correction on mapping order of CSI report |
Huawei, HiSilicon |
| R1-2401397 |
Draft CR on power control parameters for PHR of SCell |
Huawei, HiSilicon |
| R1-2401398 |
Correction on SRS carrier switching triggered by multiple DCIs |
Huawei, HiSilicon |
| R1-2401399 |
Draft CR on PUCCH carrier determination for SUL |
Huawei, HiSilicon |
| R1-2401400 |
Draft CR on PUSCH carrier determination for SUL |
Huawei, HiSilicon |
| R1-2401407 |
Clarify several ambiguities with type 2 CG-PUSCH |
Qualcomm Incorporated |
| R1-2401408 |
Clarification on SUL |
Qualcomm Incorporated |
| R1-2401409 |
Issues on SRS carrier switching |
Qualcomm Incorporated |
| R1-2401410 |
Correction on SRS carrier switching prioritization rules |
Qualcomm Incorporated |
| R1-2401411 |
Clarification on CSI dropping with UCI multiplexing on PUSCH |
Qualcomm Incorporated |
| R1-2401412 |
Clarification on typeA SRS TPC commands for SUL |
Qualcomm Incorporated |
| R1-2401413 |
CSI multiplexing behavior when multi-CSI-PUCCH-ResourceList is not provided |
Qualcomm Incorporated |
| R1-2401414 |
Correction to SL transmission power without an RSRP report |
Qualcomm Incorporated |
| R1-2401555 |
Moderator summary #1 on clarification on CSI dropping with UCI multiplexing on PUSCH |
Moderator (Qualcomm) |
| R1-2401556 |
Moderator summary #1 of clarifying several ambiguities with type 2 CG-PUSCH |
Moderator (Qualcomm) |
| R1-2401575 |
Summary of NR maintenance discussion for aperiodic triggering support for SRS carrier switching |
Moderator (Ericsson) |
| R1-2401657 |
Correction on SRS carrier switching prioritization rules |
Qualcomm Incorporated, Samsung |
| R1-2401658 |
Correction on SRS carrier switching prioritization rules |
Qualcomm Incorporated, Samsung |
| R1-2401659 |
Clarification on typeA SRS TPC commands for SUL |
Qualcomm Incorporated, Samsung |
| R1-2401660 |
Clarification on typeA SRS TPC commands for SUL |
Qualcomm Incorporated, Samsung |
| R1-2401664 |
Summary#1 of discussion on SRS transmission occasion and power scaling |
Moderator (vivo) |
| R1-2401666 |
Discussion on R1-2401412 & R1-2401410 |
Moderator (Qualcomm) |
| R1-2401683 |
[116-R15/16-NR] Summary on SCell Type 1 virtual PHR report derivation |
Moderator (Nokia) |
| R1-2401684 |
Clarification on SCell Type 1 virtual PHR reporting in UL CA |
Nokia |
| R1-2401685 |
[116-R15/16-NR] Summary on Clarification to multi-CSI-PUCCH-ResourceList |
Moderator (Nokia) |
| R1-2401686 |
[116-R15/16-NR] Summary of TBS limitation for reserved MCS retransmissions |
Moderator (Nokia) |
| R1-2401687 |
[116-R15/16-NR] Summary of ssb-index-RSRP/SINR CSI report dropping due to absence of CSI-RS |
Moderator (Nokia) |
| R1-2401688 |
ssb-index-RSRP CSI report dropping due to absence of CSI-RS |
Nokia, Nokia, Nokia Shanghai Bell |
| R1-2401689 |
ssb-index-RSRP CSI report dropping due to absence of CSI-RS |
Nokia, Nokia, Nokia Shanghai Bell |
| R1-2401690 |
ssb-index-RSRP CSI report dropping due to absence of CSI-RS |
Nokia, Nokia, Nokia Shanghai Bell |
| R1-2401691 |
[116-R15/16-NR] Summary of Clarification on not multiplexing UCI on MSG3 PUSCH |
Moderator (Nokia) |
| R1-2401697 |
FL summary on follow up discussion on CSI feedback with SUL |
Moderator (Qualcomm) |
| R1-2401700 |
Summary of discussion on the timeline issue for UCI multiplexing during HARQ-ACK overriding procedure |
Moderator (Samsung) |
| R1-2401701 |
Summary of discussion on the multiplexing prioritization for a PUSCH without a TB |
Moderator (Samsung) |
| R1-2401747 |
Summary#2 of NR maintenance discussion for aperiodic triggering support for SRS carrier switching |
Moderator (Ericsson) |
| R1-2401773 |
Summary on discussion on mapping order of CSI report |
Moderator (Huawei) |
| R1-2401793 |
Moderator summary #2 on clarification on CSI dropping with UCI multiplexing on PUSCH |
Moderator (Qualcomm) |
| R1-2401794 |
Moderator summary #2 of clarifying several ambiguities with type 2 CG-PUSCH |
Moderator (Qualcomm) |
| R1-2401809 |
Discussion summary of maximum number of PDCCH candidates determination for CSS |
Moderator (xiaomi) |
| R1-2401820 |
Summary on PUSCH Rate Matching |
Moderator (Google) |
| R1-2401829 |
Correction to SL transmission power without an RSRP report |
Qualcomm, Samsung, ZTE, OPPO, CATT CICTCI, NTT DOCOMO Inc., Apple |
| R1-2401830 |
Correction to SL transmission power without an RSRP report |
Qualcomm, Samsung, ZTE, OPPO, CATT CICTCI, NTT DOCOMO Inc., Apple |
| R1-2401831 |
Correction to SL transmission power without an RSRP report |
Qualcomm, Samsung, ZTE, OPPO, CATT CICTCI, NTT DOCOMO Inc., Apple |
| R1-2401832 |
Summary of Discussion on SL PL-based OLPC |
Moderator (Qualcomm) |
| R1-2401838 |
Clarification on SCell Type 1 virtual PHR reporting in UL CA |
Nokia, Nokia Shanghai Bell, Ericsson, Huawei, HiSilicon, New H3C Technologies Co., Ltd., Samsung, ZTE |
| R1-2401839 |
Clarification on SCell Type 1 virtual PHR reporting in UL CA |
Nokia, Nokia Shanghai Bell, Ericsson, Huawei, HiSilicon, New H3C Technologies Co., Ltd., Samsung, ZTE |
| R1-2401841 |
Draft CR on overlapping SRS resources |
vivo, Samsung |
| R1-2401842 |
Summary#2 of discussion on SRS transmission occasion and power scaling |
Moderator (vivo) |
| R1-2401852 |
Summary#3 of NR maintenance discussion for aperiodic triggering support for SRS carrier switching |
Moderator (Ericsson) |
| R1-2401853 |
Correction on SRS carrier switching prioritization rules |
Qualcomm Incorporated, Samsung |
| R1-2401854 |
Correction on SRS carrier switching prioritization rules |
Qualcomm Incorporated |
| R1-2401858 |
ssb-index-RSRP/SINR CSI report dropping due to absence of CSI-RS |
Nokia, Nokia Shanghai Bell, Samsung |
| R1-2401859 |
ssb-index-RSRP/SINR CSI report dropping due to absence of CSI-RS |
Nokia, Nokia Shanghai Bell, Samsung |
| R1-2401860 |
ssb-index-RSRP/SINR CSI report dropping due to absence of CSI-RS |
Nokia, Nokia Shanghai Bell, Samsung |
| R1-2401864 |
CR on overlapping SRS resources |
Moderator (vivo), Samsung, Ericsson, Nokia, CATT, Google |
| R1-2401865 |
CR on overlapping SRS resources |
Moderator (vivo), Samsung, Ericsson, Nokia, CATT, Google |
| R1-2401867 |
Correction on mapping order of CSI report |
Moderator (Huawei), HiSilicon, Samsung, Nokia, Nokia Shanghai Bell, New H3C, Ericsson, vivo |
| R1-2401868 |
Correction on mapping order of CSI report |
Moderator (Huawei), HiSilicon, Samsung, Nokia, Nokia Shanghai Bell, New H3C, Ericsson, vivo |
| R1-2401869 |
Correction on mapping order of CSI report |
Moderator (Huawei), HiSilicon, Samsung, Nokia, Nokia Shanghai Bell, New H3C, Ericsson, vivo |
| 7.2 |
Maintenance on NR Release 17 |
|
| R1-2400128 |
Draft CR on fallback Type-1 HARQ codebook |
Huawei, HiSilicon |
| R1-2400143 |
Discussion on the maintenance issues for Rel-17 MBS |
Huawei, HiSilicon |
| R1-2400157 |
Discussion on power control parameters for PHR of SCell |
New H3C Technologies Co., Ltd. |
| R1-2400216 |
Draft CR on type 1 codebook with MBS PDSCH repetition |
vivo |
| R1-2400284 |
Draft CR on clarifying condition for applying unified TCI |
ZTE |
| R1-2400285 |
Discussion on available slot offset for AP-SRS carrier switching |
ZTE |
| R1-2400287 |
Draft CR on Type-1 codebook for MBS and unicast |
ZTE |
| R1-2400288 |
Draft CR on Type-1 HARQ-ACK codebook for MBS |
ZTE, CBN |
| R1-2400289 |
Draft CR on DCI fields assumption with disabled HARQ-ACK information |
ZTE, CBN |
| R1-2400290 |
Draft CR on PDSCH processing timeline for MBS with disabled HARQ-ACK feedback |
ZTE |
| R1-2400291 |
Draft CR on the last multicast DCI for PUCCH resource determination |
ZTE, CBN |
| R1-2400405 |
Draft CR on PDSCH processing timeline |
CATT, CBN, China Broadnet |
| R1-2400449 |
Editorial modification on clause 8.1.4A of TS 38.214 |
CATT, CICTCI |
| R1-2400477 |
Draft CR on reportQuantity for RSRP/SINR in TS38.212 |
NEC |
| R1-2400481 |
Correction on RedCap OFDM baseband signal generation for PRACH |
ZTE, Sanechips |
| R1-2400482 |
Correction on RedCap OFDM baseband signal generation for PRACH |
ZTE, Sanechips |
| R1-2400502 |
Addition of missing parameter dl-DataToUL-ACK-v1700 |
ROHDE & SCHWARZ, Toyota ITC |
| R1-2400503 |
Addition of missing parameter dl-DataToUL-ACK-v1700 |
ROHDE & SCHWARZ, Toyota ITC |
| R1-2400506 |
Draft CR on multicast repetition for Type-1 HARQ-ACK codebook |
CATT, CBN, China Broadnet |
| R1-2400641 |
Draft CR on Timing correction for aperiodic SRS transmission |
ROHDE & SCHWARZ |
| R1-2400642 |
Draft CR on Timing correction for aperiodic SRS transmission |
ROHDE & SCHWARZ |
| R1-2400761 |
Draft CR on aperiodic SRS carrier switching |
Fujitsu |
| R1-2400869 |
Correction on HD-FDD |
NEC |
| R1-2400892 |
On antenna ports used for transmission of NCD-SSB |
Ericsson |
| R1-2400893 |
Draft Rel-17 CR for antenna ports used for transmission of NCD-SSB |
Ericsson |
| R1-2400894 |
Draft Rel-18 CR for antenna ports used for transmission of NCD-SSB |
Ericsson |
| R1-2400936 |
Draft CR on NCJT CSI-IM restriction |
Nokia, Nokia Shanghai Bell |
| R1-2400965 |
Remaining issues for MBS |
Nokia, Nokia Shanghai Bell |
| R1-2400966 |
Draft CR on Type-1 HARQ-ACK codebook with Repetitions |
Nokia, Nokia Shanghai Bell |
| R1-2401070 |
Correction for SRS transmission collision rule in RRC_INACTIVE |
ZTE |
| R1-2401071 |
Timeline for positioning SRS in RRC_INACTIVE mode |
ZTE |
| R1-2401072 |
Discussion on timeline for positioning SRS in RRC_INACTIVE mode |
ZTE |
| R1-2401088 |
Draft CR on sub-set of {DL TCI, UL TCI} indication for Rel-17 TCI framework |
NTT DOCOMO, INC. |
| R1-2401089 |
Draft CR on TCI state indication for Rel-15/16 TCI framework |
NTT DOCOMO, INC. |
| R1-2401090 |
Draft CR on determination of processing time for MBS PDSCH without feedback |
NTT DOCOMO, INC. |
| R1-2401372 |
Correction on actual time domain window for DMRS bundling |
Ericsson |
| R1-2401374 |
Draft CR on PDSCH processing timeline |
Huawei, HiSilicon |
| R1-2401391 |
Discussion on remaining issues for RedCap |
Huawei, HiSilicon |
| R1-2401396 |
Correction on Case 1 dormancy operation with data scheduling |
Huawei, HiSilicon |
| R1-2401415 |
Draft CR on Type-1 HARQ-ACK codebook for multicast with repetitions |
Qualcomm Incorporated |
| R1-2401465 |
Discussion on NCJT CSI-IM restriction |
Nokia, Nokia Shanghai Bell |
| R1-2401566 |
Moderator Summary #1 on clarifying condition for applying unified TCI |
Moderator (ZTE) |
| R1-2401576 |
Discussion summary for correction on actual time domain window for DMRS bundling |
Moderator (Ericsson) |
| R1-2401593 |
FLS #1 on positioning SRS in RRC_INACTIVE mode |
Moderator (ZTE) |
| R1-2401600 |
FLS#1 on the maintenance issues for Rel-17 NR MBS |
Moderator (Huawei) |
| R1-2401601 |
FLS#2 on the maintenance issues for Rel-17 NR MBS |
Moderator (Huawei) |
| R1-2401602 |
Draft CR on fallback Type-1 HARQ-ACK codebook on PUCCH |
Moderator (Huawei) |
| R1-2401603 |
Draft CR on Type-1 HARQ-ACK codebook |
Moderator (Huawei) |
| R1-2401604 |
Draft CR on PDSCH processing timeline |
Moderator (Huawei) |
| R1-2401605 |
Moderator summary for CSS configuration restriction for R17 RedCap |
Moderator (Huawei) |
| R1-2401606 |
Moderator summary for Case 1 dormancy operation |
Moderator (Huawei) |
| R1-2401617 |
Summary regarding correction on HD-FDD |
Moderator (NEC) |
| R1-2401623 |
Moderator summary reportQuantity for RSRP/SINR based on SSB |
Moderator (NEC) |
| R1-2401624 |
Moderator summary#1 for draft CR on NCD-SSB antenna ports |
Moderator (Ericsson) |
| R1-2401655 |
CR on Timing correction for aperiodic SRS transmission |
ROHDE & SCHWARZ |
| R1-2401656 |
CR on Timing correction for aperiodic SRS transmission |
ROHDE & SCHWARZ |
| R1-2401667 |
Moderator summary#2 for CSS configuration restriction for R17 RedCap |
Moderator (Huawei) |
| R1-2401692 |
FLS #2 on positioning SRS in RRC_INACTIVE mode |
Moderator (ZTE) |
| R1-2401693 |
Correction for SRS transmission collision rule in RRC_INACTIVE |
Moderator (ZTE) |
| R1-2401694 |
Correction for SRS transmission collision rule in RRC_INACTIVE |
Moderator (ZTE) |
| R1-2401719 |
CR on reportQuantity for RSRP/SINR in TS38.212 |
Moderator (NEC), Samsung |
| R1-2401720 |
CR on reportQuantity for RSRP/SINR in TS38.212 |
Moderator (NEC), Samsung |
| R1-2401721 |
Clarification on NCJT CSI-IM restriction |
Moderator (Nokia), Samsung |
| R1-2401722 |
Clarification on NCJT CSI-IM restriction |
Moderator (Nokia), Samsung |
| R1-2401725 |
Moderator summary on NCJT CSI-IM restriction |
Moderator (Nokia) |
| R1-2401733 |
Correction on actual time domain window for DMRS bundling |
Ericsson |
| R1-2401734 |
Correction on actual time domain window for DMRS bundling |
Ericsson |
| R1-2401736 |
Correction on the support of SCI format 1-A in IUC scheme 1 |
CATT, CICTCI |
| R1-2401737 |
Correction on the support of SCI format 1-A in IUC scheme 1 |
CATT, CICTCI |
| R1-2401738 |
CR on sub-set of {DL TCI, UL TCI} indication for Rel-17 TCI framework |
NTT DOCOMO, INC., Samsung, ZTE |
| R1-2401739 |
CR on sub-set of {DL TCI, UL TCI} indication for Rel-17 TCI framework |
NTT DOCOMO, INC., Samsung, ZTE |
| R1-2401740 |
CR on TCI state indication for Rel-15/16 TCI framework |
NTT DOCOMO, INC., Samsung |
| R1-2401741 |
CR on TCI state indication for Rel-15/16 TCI framework |
NTT DOCOMO, INC., Samsung |
| R1-2401744 |
Correction on Case 1 dormancy operation with data scheduling |
Huawei, HiSilicon |
| R1-2401745 |
Correction on Case 1 dormancy operation with data scheduling |
Huawei, HiSilicon |
| R1-2401749 |
Correction for SRS transmission collision rule in RRC_INACTIVE |
Moderator (ZTE) |
| R1-2401750 |
Correction for SRS transmission collision rule in RRC_INACTIVE |
Moderator (ZTE) |
| R1-2401757 |
Session notes for 7.2 (Maintenance on NR Release 17) |
Ad-Hoc Chair (Huawei) |
| R1-2401770 |
Draft CR on fallback Type-1 HARQ-ACK codebook on PUCCH |
Moderator (Huawei) |
| R1-2401771 |
Draft CR on Type-1 HARQ-ACK codebook |
Moderator (Huawei) |
| R1-2401772 |
Draft CR on PDSCH processing timeline |
Moderator (Huawei) |
| R1-2401777 |
CR on clarifying condition for applying unified TCI |
ZTE, Samsung |
| R1-2401778 |
CR on clarifying condition for applying unified TCI |
ZTE, Samsung |
| R1-2401786 |
CR on clarifying condition for applying unified TCI |
ZTE, Samsung |
| R1-2401811 |
CR on Timing correction for aperiodic SRS transmission |
ROHDE & SCHWARZ, Ericsson |
| R1-2401812 |
CR on Timing correction for aperiodic SRS transmission |
ROHDE & SCHWARZ, Ericsson |
| R1-2401815 |
CR on PDSCH processing timeline |
Moderator (Huawei), ZTE, vivo, Samsung, DOCOMO, CATT, Qualcomm, Nokia |
| R1-2401816 |
CR on PDSCH processing timeline |
Moderator (Huawei), ZTE, vivo, Samsung, DOCOMO, CATT, Qualcomm, Nokia |
| R1-2401866 |
RAN1 agreements for Rel-17 NR RedCap |
Rapporteur (Ericsson) |
| R1-2401873 |
Summary of discussion on RedCap OFDM baseband signal generation for PRACH |
Moderator (ZTE) |
| R1-2401879 |
Rel-16 editorial corrections for TS 38.212 (mirrored to Rel-17) |
Huawei |
| R1-2401880 |
Rel-16 editorial corrections for TS 38.212 (mirrored to Rel-18) |
Huawei |
| R1-2401881 |
Rel-16 editorial corrections for TS 38.212 |
Huawei |
| R1-2401882 |
Rel-17 editorial corrections for TS 38.214 – mirror to Rel-18 |
Nokia |
| R1-2401883 |
Rel-17 editorial corrections for TS 38.214 |
Nokia |
| R1-2401886 |
Rel-17 editorial corrections for TS 38.213 |
Samsung |
| R1-2401887 |
Rel-17 editorial corrections for TS 38.213 (mirrored to Rel-18) |
Samsung |
| R1-2401911 |
Alignment of parameter names |
Ericsson |
| R1-2401912 |
Alignment of parameter names |
Ericsson |
| 8 |
Maintenance on Release 18 |
|
| R1-2401875 |
Maintenance of network energy savings for NR |
Samsung |
| R1-2401876 |
Correction of specification support for network energy saving |
Nokia |
| R1-2401877 |
Maintenance of BWP operation without restriction |
Samsung |
| R1-2401878 |
Maintenance of further NR coverage enhancements |
Samsung |
| R1-2401884 |
Corrections of NR support for dedicated spectrum less than 5MHz for FR1 |
Nokia |
| R1-2401885 |
Rel-18 editorial corrections for TS 38.212 |
Huawei |
| R1-2401888 |
Corrections on Rel-18 Multi-carrier enhancements in 38.212 |
Huawei |
| R1-2401889 |
Corrections on Rel-18 MIMO Evolution for Downlink and Uplink in 38.212 |
Huawei |
| R1-2401890 |
Maintenance of multi-carrier enhancements for NR |
Samsung |
| R1-2401891 |
Corrections on Multi-Carrier Enhancements for NR |
Nokia |
| R1-2401892 |
Corrections on Multi-Carrier Enhancements for NR |
Nokia |
| R1-2401893 |
Corrections to MIMO enhancements |
Ericsson |
| R1-2401894 |
Maintenance of MIMO Evolution for Downlink and Uplink |
Samsung |
| R1-2401895 |
Correction of specification support for MIMO enhancements |
Nokia |
| R1-2401896 |
Corrections on Rel-18 MIMO Evolution for Downlink and Uplink in 38.212 |
Huawei |
| R1-2401897 |
Maintenance of further mobility enhancements |
Samsung |
| R1-2401898 |
Corrections of specification support for mobility enhancements |
Nokia |
| R1-2401899 |
Corrections of specification support for mobility enhancements |
Nokia |
| R1-2401900 |
Corrections of specification support for mobility enhancements |
Nokia |
| R1-2401901 |
Maintenance of Network Controlled Repeaters |
Samsung |
| R1-2401902 |
Maintenance of support for NR NTN enhancements |
Samsung |
| R1-2401903 |
Correction of Rel-18 NTN enhancements |
Intel Corporation |
| R1-2401904 |
Release 18 TS38.202 Editor CR for simultaneous SL-PRS transmission and Reception |
Qualcomm |
| R1-2401905 |
Corrections to positioning enhancements |
Ericsson |
| R1-2401906 |
Corrections on NR positioning enhancement in 38.212 |
Huawei |
| R1-2401907 |
Maintenance of expanded and improved NR positioning |
Samsung |
| R1-2401908 |
Corrections on the support for Expanded and Improved NR Positioning |
Nokia |
| R1-2401909 |
Correction of Rel-18 positioning enhancements |
Intel Corporation |
| R1-2401910 |
Maintenance of support for enhanced reduced capability NR devices |
Samsung |
| R1-2401913 |
Maintenance of NR Sidelink operation on shared spectrum |
Ericsson |
| R1-2401914 |
Corrections to sidelink enhancements |
Ericsson |
| R1-2401915 |
Corrections on Rel-18 NR sidelink evolution in 38.212 |
Huawei |
| R1-2401916 |
Maintenance of NR sidelink evolution |
Samsung |
| R1-2401917 |
Correction of enhancements for NR sidelink evolution |
Nokia |
| R1-2401918 |
Correction of Rel-18 sidelink evolution |
Intel Corporation |
| R1-2401919 |
Corrections of XR Enhancements for NR |
Nokia |
| R1-2401920 |
Introduction of multiplexing in a PUSCH with repetitions HARQ-ACK associated with DL assignments received after an UL grant for the PUSCH [HARQ-ACK MUX on PUSCH] |
Samsung |
| R1-2401922 |
RedCap CFR for MBS broadcast [RedCapMBS_Bcast] |
Samsung |
| R1-2401923 |
Editor’s summary on draft CR 37.213 for SL-U |
Ericsson |
| R1-2401924 |
Summary of email discussions [Post-116-38.213-NR_MC_Enh] |
Samsung |
| R1-2401925 |
Summary of email discussions [Post-116-38.213-NR_MIMO_evo_DL_UL] |
Samsung |
| R1-2401926 |
Summary of email discussions [Post-116-38.213-NR_mob_enh2] |
Samsung |
| R1-2401927 |
Summary of email discussions [Post-116-38.213-NR_redcap_enh] |
Samsung |
| R1-2401928 |
Summary of email discussions [Post-116-38.213-NR_SL_enh2] |
Samsung |
| R1-2401929 |
RedCap CFR for MBS broadcast [RedCapMBS_Bcast] |
Samsung |
| 8.1 |
Maintenance on NR MIMO Evolution for Downlink and Uplink |
|
| R1-2400036 |
Remaining issues on NR MIMO Evolution for Downlink and Uplink |
Spreadtrum Communications |
| R1-2400102 |
Maintenance of Rel-18 MIMO |
Huawei, HiSilicon |
| R1-2400160 |
Maintenance on Rel-18 CSI enhancements |
New H3C Technologies Co., Ltd. |
| R1-2400192 |
Maintenance on NR MIMO Evolution for Downlink and Uplink |
Lenovo |
| R1-2400217 |
Maintenance on Rel-18 NR MIMO Evolution |
vivo |
| R1-2400275 |
Maintenance on NR MIMO Evolution for Downlink and Uplink |
ZTE |
| R1-2400309 |
Maintenance on NR MIMO evolution for downlink and uplink |
CMCC |
| R1-2400390 |
Maintenance on NR MIMO Evolution |
Google |
| R1-2400406 |
Maintenance on Rel-18 NR MIMO Evolution |
CATT |
| R1-2400519 |
Maintenance on NR MIMO evolution |
Ericsson |
| R1-2400531 |
Maintenance on NR MIMO Evolution for Downlink and Uplink |
xiaomi |
| R1-2400578 |
Text proposals on NR MIMO Evolution for Downlink and Uplink |
OPPO |
| R1-2400679 |
Maintenance on NR MIMO Evolution for Downlink and Uplink |
Langbo |
| R1-2400704 |
Maintenance issues for Rel-18 NR MIMO |
Samsung |
| R1-2400754 |
Maintenance on NR MIMO Evolution for Downlink and Uplink |
MediaTek Inc. |
| R1-2400762 |
Discussion on maintenance issues of Rel-18 MIMO |
Fujitsu |
| R1-2400782 |
Moderator summary for maintenance issues on Rel-18 MIMO CSI enhancements |
Moderator (Samsung) |
| R1-2400913 |
Maintenance on Rel-18 MIMO |
LG Electronics |
| R1-2400937 |
Maintenance on NR MIMO Evolution for Downlink and Uplink |
Nokia, Nokia Shanghai Bell |
| R1-2401048 |
Maintenance on NR MIMO Evolution for Downlink and Uplink |
Sharp |
| R1-2401091 |
Maintenance on NR MIMO Evolution for Downlink and Uplink |
NTT DOCOMO, INC. |
| R1-2401416 |
Maintenance on NR MIMO Evolution for Downlink and Uplink |
Qualcomm Incorporated |
| R1-2401482 |
FL summary on DMRS#1 |
Moderator (NTT DOCOMO) |
| R1-2401483 |
FL summary on DMRS#2 |
Moderator (NTT DOCOMO) |
| R1-2401488 |
Summary on Rel-18 STxMP |
Moderator (OPPO) |
| R1-2401527 |
FL Summary #1 on SRS enhancements |
Moderator (FUTUREWEI) |
| R1-2401528 |
FL Summary #2 on SRS enhancements |
Moderator (FUTUREWEI) |
| R1-2401564 |
Moderator summary for maintenance of Rel-18 MIMO on unified TCI extension (Round 0) |
Moderator (MediaTek Inc.) |
| R1-2401577 |
FL Summary on Maintenance for 8TX; First Round |
Moderator (InterDigital, Inc.) |
| R1-2401581 |
Moderator Summary #1 on Two TAs for multi-DCI |
Moderator (Ericsson) |
| R1-2401632 |
Moderator summary for maintenance of Rel-18 MIMO on unified TCI extension (Round 1) |
Moderator (MediaTek Inc.) |
| R1-2401672 |
FL Summary on Maintenance for 8TX; Second Round |
Moderator (InterDigital, Inc.) |
| R1-2401699 |
Moderator Summary #2 on Two TAs for multi-DCI |
Moderator (Ericsson) |
| 8.2 |
Maintenance on NR Sidelink Evolution |
|
| R1-2400037 |
Remaining issues on NR Sidelink Evolution |
Spreadtrum Communications |
| R1-2400096 |
Maintenance of NR sidelink evolution |
FUTUREWEI |
| R1-2400130 |
Maintenance of Rel-18 NR sidelink evolution |
Huawei, HiSilicon |
| R1-2400199 |
Maintenance on NR Sidelink Evolution |
Lenovo |
| R1-2400203 |
Remaining issues for sidelink in unlicensed spectrum |
Transsion Holdings |
| R1-2400218 |
Maintenance on Rel-18 SL-Evo |
vivo |
| R1-2400367 |
Maintenance of Rel-18 NR Sidelink Evolution NR_SL_enh2 |
Nokia, Nokia Shanghai Bell |
| R1-2400408 |
Remaining issues on Rel-18 NR Sidelink Evolution |
CATT, CICTCI |
| R1-2400457 |
Remaining Issues and TP on Sidelink Evolution |
NEC |
| R1-2400538 |
Maintenance on Sidelink Evolution |
xiaomi |
| R1-2400582 |
Remaining maintenance issues for R18 NR sidelink evolution WI |
OPPO |
| R1-2400638 |
Maintenance on NR sidelink evolution |
ZTE, Sanechips |
| R1-2400711 |
Maintenance on NR Sidelink Evolution |
Samsung |
| R1-2400786 |
Remaining issues on NR sidelink evolution |
LG Electronics |
| R1-2400988 |
On Remaining Issues of Release 18 NR Sidelink |
Apple |
| R1-2401051 |
Maintenance of NR Sidelink unlicensed spectrum |
Panasonic |
| R1-2401092 |
Maintenance of NR SL evolution |
NTT DOCOMO, INC. |
| R1-2401165 |
Maintenance on NR Sidelink Evolution |
Sharp |
| R1-2401202 |
Discussion on channel design for SL-U |
ASUSTeK |
| R1-2401213 |
Maintenance of Rel-18 NR sidelink evolution |
WILUS |
| R1-2401320 |
On maintenance for NR sidelink evolution |
MediaTek Inc. |
| R1-2401417 |
Maintenance on NR Sidelink Evolution |
Qualcomm Incorporated |
| R1-2401506 |
FL Summary #1 for AI 8.2: Co-channel coexistence for LTE sidelink and NR sidelink |
Moderator (LG Electronics) |
| R1-2401507 |
FL Summary #2 for AI 8.2: Co-channel coexistence for LTE sidelink and NR sidelink |
Moderator (LG Electronics) |
| R1-2401508 |
FL Summary #1 for AI 8.2: Sidelink CA operation |
Moderator (LG Electronics) |
| R1-2401509 |
FL Summary #2 for AI 8.2: Sidelink CA operation |
Moderator (LG Electronics) |
| R1-2401522 |
FL summary#1 for AI 8.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2401523 |
FL summary#2 for AI 8.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2401524 |
FL summary#3 for AI 8.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2401525 |
FL summary#4 for AI 8.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2401526 |
FL summary#5 for AI 8.2 SL-U physical channel design framework |
Moderator (Huawei) |
| R1-2401529 |
FL summary #1 for AI 8.2: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2401530 |
FL summary #2 for AI 8.2: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2401531 |
FL summary #3 for AI 8.2: SL-U channel access mechanism |
Moderator (OPPO) |
| R1-2401532 |
FL summary for AI 8.2: SL-U channel access mechanism (EOM) |
Moderator (OPPO) |
| R1-2401622 |
FL Summary #3 for AI 8.2: Sidelink CA operation |
Moderator (LG Electronics) |
| R1-2401726 |
Draft Reply to LS on Sidelink CSI Reporting MAC-CE for SL-CA |
Moderator (LG Electronics) |
| R1-2401727 |
Reply to LS on Sidelink CSI Reporting MAC-CE for SL-CA |
RAN1, LG Electronics |
| R1-2401755 |
Draft LS on new higher layer parameter for intra-cell guard band |
Moderator (OPPO) |
| R1-2401756 |
LS on new higher layer parameter for intra-cell guard band |
RAN1, OPPO |
| R1-2401758 |
Session notes for 8.2 (Maintenance on NR sidelink evolution) |
Ad-Hoc Chair (Huawei) |
| 8.3 |
Maintenance on Expanded and Improved NR Positioning |
|
| R1-2400138 |
Maintenance of expanded and improved NR positioning |
Huawei, HiSilicon |
| R1-2400191 |
Remaining issues on NR Positioning |
Nokia, Nokia Shanghai Bell |
| R1-2400219 |
Maintenance on Rel-18 Positioning |
vivo |
| R1-2400310 |
Maintenance on expanded and improved NR positioning |
CMCC |
| R1-2400374 |
Maintenance issues on Rel-18 Positioning |
Intel Corporation |
| R1-2400409 |
Maintenance on Expanded and Improved NR Positioning |
CATT, CICTCI |
| R1-2400539 |
Maintenance on Expanded and Improved NR Positioning |
xiaomi |
| R1-2400580 |
Text Proposals on Expanded and Improved NR Positioning |
OPPO |
| R1-2400708 |
Maintenance on Expanded and Improved NR Positioning |
Samsung |
| R1-2400989 |
Remaining Issues On Expanded and Improved Positioning |
Apple |
| R1-2401039 |
Discussion on remaining issues for R18 NR positioning |
InterDigital, Inc. |
| R1-2401073 |
Maintenance on expanded and improved NR positioning |
ZTE |
| R1-2401162 |
Maintenance on Resource allocation for SL PRS |
ASUSTeK |
| R1-2401247 |
Maintenance of expanded and improved NR positioning |
LG Electronics |
| R1-2401351 |
Remaining issues on expanded and improved NR positioning |
Ericsson |
| R1-2401418 |
Maintenance on Expanded and Improved NR Positioning |
Qualcomm Incorporated |
| R1-2401485 |
FL Summary #1 for maintenance on NR DL and UL carrier phase positioning |
Moderator (CATT) |
| R1-2401486 |
FL Summary #2 for maintenance on NR DL and UL carrier phase positioning |
Moderator (CATT) |
| R1-2401487 |
FL Summary #3 for maintenance on NR DL and UL carrier phase positioning |
Moderator (CATT) |
| R1-2401547 |
FL summary #1 on SL positioning reference signal |
Moderator (Intel Corporation) |
| R1-2401548 |
FL summary #2 on SL positioning reference signal |
Moderator (Intel Corporation) |
| R1-2401549 |
FL summary #3 on SL positioning reference signal |
Moderator (Intel Corporation) |
| R1-2401550 |
Moderator summary #1 on RAN2 LS on MAC agreements for SL Positioning |
Moderator (Intel Corporation) |
| R1-2401551 |
Draft Reply LS on MAC agreements for SL Positioning |
Moderator (Intel Corporation) |
| R1-2401552 |
Reply LS on MAC agreements for SL Positioning |
RAN1, Intel Corporation |
| R1-2401594 |
Summary #1 for BW aggregation positioning |
Moderator (ZTE) |
| R1-2401595 |
Summary #2 for BW aggregation positioning |
Moderator (ZTE) |
| R1-2401608 |
Moderator Summary #0 on resource allocation for SL PRS |
Moderator (Qualcomm) |
| R1-2401611 |
Summary #1 on Measurements and reporting for SL positioning |
Moderator (vivo) |
| R1-2401612 |
Summary #2 on Measurements and reporting for SL positioning |
Moderator (vivo) |
| R1-2401613 |
Summary #3 on Measurements and reporting for SL positioning |
Moderator (vivo) |
| R1-2401628 |
Summary #1 for low power high accuracy positioning |
Moderator (CMCC) |
| R1-2401636 |
Feature Lead summary #1 for Positioning for RedCap Ues |
Moderator (Ericsson) |
| R1-2401637 |
Feature Lead summary #2 for Positioning for RedCap Ues |
Moderator (Ericsson) |
| R1-2401638 |
Feature Lead summary #3 for Positioning for RedCap Ues |
Moderator (Ericsson) |
| R1-2401680 |
Moderator Summary #1 on resource allocation for SL PRS |
Moderator (Qualcomm) |
| R1-2401707 |
Draft LS on bandwidth aggregation for positioning |
Moderator (ZTE) |
| R1-2401708 |
LS on bandwidth aggregation for positioning |
RAN1, ZTE |
| R1-2401759 |
Session notes for 8.3 (Maintenance on expanded and improved NR positioning) |
Ad-Hoc Chair (Huawei) |
| R1-2401792 |
Moderator Summary #2 on resource allocation for SL PRS |
Moderator (Qualcomm) |
| R1-2401800 |
Draft LS on the bandwidth used in measurements for positioning of RedCap UEs |
Ericsson |
| R1-2401801 |
LS on the bandwidth used in measurements for positioning of RedCap UEs |
RAN1, Ericsson |
| R1-2401826 |
Draft LS on higher layer parameters for SL Positioning |
Moderator (Intel Corporation), Moderator (Qualcomm) |
| R1-2401827 |
LS on higher layer parameters for SL Positioning |
RAN1, Intel Corporation, Qualcomm |
| R1-2401828 |
List of RAN1 agreements for Rel-18 Positioning |
Moderator (Intel Corporation) |
| 8.4 |
Maintenance on Network Energy Savings for NR |
|
| R1-2400122 |
Maintenance of Rel-18 NES |
Huawei, HiSilicon |
| R1-2400183 |
Maintenance on Network Energy Savings for NR |
Nokia, Nokia Shanghai Bell |
| R1-2400220 |
Maintenance on Rel-18 network energy saving |
vivo |
| R1-2400372 |
Maintenance issues on NES |
Intel Corporation |
| R1-2400391 |
Maintenance on NES |
Google |
| R1-2400410 |
Remaining Issues in Rel-18 Network Energy Saving |
CATT |
| R1-2400485 |
Remaining issues on Rel-18 NES techniques |
ZTE, Sanechips |
| R1-2400540 |
Remaining issues on network energy saving |
xiaomi |
| R1-2400588 |
Discussion on maintenance on network energy saving for NR |
OPPO |
| R1-2400709 |
Remaining issues on network energy saving |
Samsung |
| R1-2400900 |
Remaining issues of Rel-18 network energy saving |
Panasonic |
| R1-2400990 |
Maintenance of Network Energy Savings for NR |
Apple |
| R1-2401139 |
Maintenance for Rel-18 network energy savings |
Ericsson |
| R1-2401185 |
Correction on cell DTX DRX |
ASUSTeK |
| R1-2401186 |
Maintenance of UE procedure for determining physical downlink control channel assignment |
ITRI |
| R1-2401316 |
Maintenance on Network Energy Savings for NR |
MediaTek Inc. |
| R1-2401322 |
Remaining issues on NES |
LG Electronics |
| R1-2401419 |
Maintenance on cell DTX and DRX |
Qualcomm Incorporated |
| R1-2401501 |
Summary of issues for Rel-18 NES enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2401502 |
Summary #1 of discussion for Rel-18 NES enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2401503 |
Summary #2 of discussion for Rel-18 NES enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2401533 |
FLS#1 for maintenance of SD-PD adaptation R18 NES |
Moderator (Huawei) |
| R1-2401534 |
FLS#2 for maintenance of SD-PD adaptation R18 NES |
Moderator (Huawei) |
| R1-2401751 |
Summary #3 of discussion for Rel-18 NES enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2401752 |
Summary #4 of discussion for Rel-18 NES enhancements on cell DTX/DRX mechanism |
Moderator (Intel Corporation) |
| R1-2401753 |
Draft LS on Network Energy Savings |
Moderator (Intel Corporation, Huawei) |
| R1-2401810 |
LS on Network Energy Savings |
RAN1, Intel Corporation, Huawei |
| 8.5 |
Maintenance on Further NR Mobility Enhancements |
|
| R1-2400038 |
Remaining issues on further NR Mobility Enhancements |
Spreadtrum Communications |
| R1-2400142 |
Maintenance of L1 enhancements for inter-cell beam management |
Huawei, HiSilicon |
| R1-2400186 |
FL plan for Maintenance on Further NR Mobility Enhancements at RAN1#116 |
Moderator (Fujitsu) |
| R1-2400193 |
Maintenance on further NR mobility enhancements |
Lenovo |
| R1-2400221 |
Maintenance on Further NR Mobility Enhancements |
vivo |
| R1-2400276 |
Maintenance on Further NR Mobility Enhancements |
ZTE |
| R1-2400452 |
Maintenance on NR mobility enhancements |
CATT |
| R1-2400581 |
Text Proposals on Further NR Mobility Enhancement |
OPPO |
| R1-2400646 |
Remaining Issues for L1/L2-triggered Mobility |
Nokia, Nokia Shanghai Bell |
| R1-2400680 |
Maintenance on Further NR Mobility Enhancements |
Langbo |
| R1-2400707 |
Maintenance on Further NR Mobility Enhancements |
Samsung |
| R1-2400763 |
Remaining issues on further NR mobility enhancements |
Fujitsu |
| R1-2400880 |
On missing specification on LTM TCI state configuration |
Panasonic |
| R1-2400911 |
Maintenance on Further NR Mobility Enhancements |
Ericsson |
| R1-2400991 |
Maintenance of further NR mobility enhancement |
Apple |
| R1-2401093 |
Maintenance on Further NR Mobility Enhancements |
NTT DOCOMO, INC. |
| R1-2401200 |
Discussion on early PRACH |
ASUSTeK |
| R1-2401255 |
Discussion on maintenance on further NR mobility enhancements |
Google |
| R1-2401312 |
On maintenance for mobility enhancements |
MediaTek Inc. |
| R1-2401582 |
FL summary 1 of Maintenance on Further NR Mobility Enhancements |
Moderator (Fujitsu) |
| R1-2401583 |
FL summary 2 of Maintenance on Further NR Mobility Enhancements |
Moderator (Fujitsu) |
| R1-2401760 |
Session notes for 8.5 (Maintenance on Further NR Mobility Enhancements) |
Ad-Hoc Chair (CMCC) |
| R1-2401782 |
FL summary 3 of Maintenance on Further NR Mobility Enhancements |
Moderator (Fujitsu) |
| R1-2401783 |
Final FL summary of Maintenance on Further NR Mobility Enhancements |
Moderator (Fujitsu) |
| R1-2401784 |
[draft] LS on TCI state after cell switch command for LTM |
Moderator (Fujitsu) |
| R1-2401785 |
LS on TCI state after cell switch command for LTM |
RAN1, Fujitsu |
| 8.6 |
Maintenance on Further NR Coverage Enhancements |
|
| R1-2400039 |
Remaining issues on further NR coverage enhancements |
Spreadtrum Communications |
| R1-2400112 |
Maintenance of Rel-18 Coverage Enhancements |
Huawei, HiSilicon |
| R1-2400159 |
Discussions on the remaining issue on PRACH coverage |
New H3C Technologies Co., Ltd. |
| R1-2400222 |
Maintenance on Further NR Coverage Enhancements |
vivo |
| R1-2400292 |
Maintenance of Rel-18 coverage enhancements |
ZTE |
| R1-2400359 |
Maintenance on Further NR Coverage Enhancements |
TCL |
| R1-2400368 |
Remaining issues on further NR coverage enhancement |
Intel Corporation |
| R1-2400411 |
Remaining issues on Rel-18 coverage enhancements |
CATT |
| R1-2400458 |
Maintenance on PRACH coverage enhancement |
NEC |
| R1-2400541 |
Discussion on PRACH coverage enhancements |
xiaomi |
| R1-2400593 |
Discussion on maintenance on coverage enhancement |
OPPO |
| R1-2400655 |
Remaining issues on PRACH coverage enhancement |
China Telecom |
| R1-2400706 |
Maintenance on Further NR Coverage Enhancements |
Samsung |
| R1-2400809 |
Remaining issues on further NR coverage enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2400829 |
Maintenance on further NR coverage enhancements |
Panasonic |
| R1-2400925 |
Remaining issues on dynamic switching between DFT-S-OFDM and CP-OFDM |
InterDigital, Inc. |
| R1-2400992 |
Remaining issues on further NR coverage enhancements |
Apple |
| R1-2401076 |
Maintenance of Further NR Coverage Enhancements |
Ericsson |
| R1-2401094 |
Maintenance on Further NR Coverage Enhancements |
NTT DOCOMO, INC. |
| R1-2401166 |
Remaining issues on Further NR Coverage Enhancements |
Sharp |
| R1-2401207 |
Remaining issues on PRACH coverage enhancements |
Fujitsu |
| R1-2401221 |
Maintenance on further NR coverage enhancements |
ETRI |
| R1-2401248 |
Remaining issues on Rel-18 NR coverage enhancements |
LG Electronics |
| R1-2401313 |
On maintenance for coverage enhancements |
MediaTek Inc. |
| R1-2401420 |
Maintenance on Further NR Coverage Enhancements |
Qualcomm Incorporated |
| R1-2401500 |
FL summary of Maintenance on further NR coverage enhancements (AI 8.6) - Power domain enhancements |
Moderator (Nokia) |
| R1-2401504 |
Summary #1 on dynamic switching between DFT-S-OFDM and CP-OFDM |
Moderator (InterDigital) |
| R1-2401505 |
Summary #2 on dynamic switching between DFT-S-OFDM and CP-OFDM |
Moderator (InterDigital) |
| R1-2401553 |
FL Summary #1 on remaining issues for PRACH coverage enhancements |
Moderator (China Telecom) |
| R1-2401554 |
FL Summary #2 on remaining issues for PRACH coverage enhancements |
Moderator (China Telecom) |
| R1-2401626 |
[Draft] Reply LS on UE capabilities for MPR reduction |
Moderator (Nokia) |
| R1-2401627 |
Reply LS on UE capabilities for MPR reduction |
RAN1, Nokia |
| R1-2401648 |
Draft LS on PRACH coverage enhancement |
China Telecom |
| R1-2401761 |
Session notes for 8.6 (Maintenance on further NR coverage enhancements) |
Ad-Hoc Chair (CMCC) |
| R1-2401850 |
Final FL summary of Maintenance on further NR coverage enhancements (AI 8.6) - Power domain enhancements |
Moderator (Nokia) |
| 8.7 |
Maintenance on NR Network-Controlled Repeaters |
|
| R1-2400151 |
Maintenance on NR Network-Controlled Repeaters |
Huawei, HiSilicon |
| R1-2400351 |
Remaining issue on side control information and NCR behavior |
ZTE |
| R1-2400412 |
Maintenance on NR Network-Controlled Repeaters |
CATT |
| R1-2400462 |
Maintenance on side control information and behaviour for NCR |
NEC |
| R1-2400650 |
Discussion on Maintenance on NR Network-Controlled Repeaters |
Nokia, Nokia Shanghai Bell |
| R1-2400705 |
Maintenance on NR Network-Controlled Repeaters |
Samsung |
| R1-2401241 |
Maintenance on NR Network-controlled Repeaters |
Ericsson |
| R1-2401651 |
Summary#1 of maintenance issues on side control information and NCR behavior |
Moderator (ZTE) |
| R1-2401762 |
Session notes for 8.7 (Maintenance on NR Network-Controlled Repeaters) |
Ad-Hoc Chair (CMCC) |
| 8.8 |
Maintenance on Multi-Carrier Enhancements for NR |
|
| R1-2400040 |
Remaining issues on Multi-Carrier Enhancements for NR |
Spreadtrum Communications |
| R1-2400136 |
Maintenance of Rel-18 Multicarrier Enhancements |
Huawei, HiSilicon |
| R1-2400198 |
Remaining issues on Rel-18 multi-carrier enhancements |
Lenovo |
| R1-2400223 |
Maintenance on Multi-Carrier Enhancements for NR |
vivo |
| R1-2400293 |
Maintenance on Multi-Carrier Enhancements for NR |
ZTE |
| R1-2400311 |
Remaining issues on Multi-carrier enhancements for NR |
CMCC |
| R1-2400413 |
Maintenance on Multi-Carrier Enhancements for NR |
CATT |
| R1-2400542 |
Remaining issues on Multi-Carrier Enhancements for NR |
xiaomi |
| R1-2400596 |
Remaining issues in multi-carrier enhancement for NR |
OPPO |
| R1-2400647 |
Discussion on Maintenance on NR Network-Controlled Repeaters |
Nokia, Nokia Shanghai Bell |
| R1-2400654 |
On Rel-18 MC-DCI scheduling |
Nokia, Nokia Shanghai Bell |
| R1-2400681 |
Maintenance on Multi-Carrier Enhancements for NR |
Langbo |
| R1-2400712 |
Remaining issues on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Samsung |
| R1-2400764 |
Remaining issues on SCell dormancy indication by DCI format 0_3/1_3 |
Fujitsu |
| R1-2400993 |
On maintenance issues for Rel-18 MC enhancements |
Apple |
| R1-2401095 |
Maintenance on multi-carrier enhancements |
NTT DOCOMO, INC. |
| R1-2401140 |
Maintenance for Rel-18 multi-carrier enhancements |
Ericsson |
| R1-2401289 |
On maintenance for multi-carrier enhancement |
MediaTek Inc. |
| R1-2401323 |
Remaining issues on multi-cell scheduling with single DCI |
LG Electronics |
| R1-2401510 |
Summary of discussion on Multi-carrier UL Tx switching scheme |
Moderator (NTT DOCOMO, INC.) |
| R1-2401589 |
Feature lead summary#1 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| R1-2401590 |
Feature lead summary#2 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| R1-2401591 |
Feature lead summary#3 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| R1-2401639 |
Summary#2 of discussion on Multi-carrier UL Tx switching scheme |
Moderator (NTT DOCOMO, INC.) |
| R1-2401715 |
Draft LS on TS38.300 TP for Multi-cell scheduling in Rel-18 |
NTT DOCOMO, INC. |
| R1-2401716 |
LS on TS38.300 TP for Multi-cell scheduling in Rel-18 |
RAN1, NTT DOCOMO |
| R1-2401776 |
Reply LS on UL Tx switching |
RAN1, NTT DOCOMO |
| R1-2401802 |
Summary#3 of discussion on Multi-carrier UL Tx switching scheme |
Moderator (NTT DOCOMO, INC.) |
| R1-2401848 |
Feature lead summary#4 on multi-cell PUSCH/PDSCH scheduling with a single DCI |
Moderator (Lenovo) |
| 8.9 |
Maintenance on IoT NTN enhancements |
|
| R1-2400352 |
Remaining issue on IoT-NTN |
ZTE |
| R1-2400470 |
Maintenance on disabling of HARQ feedback for IoT NTN |
NEC |
| R1-2400586 |
Discussion on maintenance on IoT NTN enhancements |
OPPO |
| R1-2400873 |
Remaining issues for IoT NTN |
Lenovo |
| R1-2400878 |
Maintenance on IoT NTN enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2400994 |
Remaining issues on IoT NTN enhancements |
Apple |
| R1-2401193 |
Maintenance on IoT NTN enhancements |
Ericsson |
| R1-2401380 |
Maintenance of Rel-18 IoT NTN |
Huawei, HiSilicon |
| R1-2401421 |
Maintenance on IOT NTN enhancements |
Qualcomm Incorporated |
| R1-2401462 |
Maintenance on IoT NTN enhancements |
Nordic Semiconductor ASA |
| R1-2401497 |
FLS#1 on disabling of HARQ feedback for IoT NTN |
Moderator (Lenovo) |
| R1-2401542 |
Feature lead summary #1 of AI 8.9 on improved GNSS operations |
Moderator (MediaTek) |
| R1-2401754 |
LS on improved GNSS operations in Rel-18 IoT NTN |
RAN1, MediaTek |
| R1-2401763 |
Session notes for 8.9 (Maintenance on IoT NTN enhancements) |
Ad-Hoc Chair (Huawei) |
| R1-2401790 |
Feature lead summary #2 of AI 8.9 on improved GNSS operations |
Moderator (MediaTek) |
| R1-2401921 |
Corrections to IoT (Internet of Things) NTN (non-terrestrial network) enhancements |
Motorola Mobility |
| 8.10 |
Maintenance on NR NTN enhancements |
|
| R1-2400224 |
Maintenance on Rel-18 NR NTN |
vivo |
| R1-2400353 |
Remaining issue on NR-NTN |
ZTE |
| R1-2400532 |
Discussion on remaining issues in NR NTN enhancements |
xiaomi |
| R1-2400587 |
Discussion on maintenance on NR NTN enhancements |
OPPO |
| R1-2400713 |
Maintenance on NR NTN enhancements |
Samsung |
| R1-2400970 |
Open aspects related to Rel-18 maintenance for NR over NTN |
Nokia, Nokia Shanghai Bell |
| R1-2400976 |
On maintenance of NR NTN enhancements |
Ericsson |
| R1-2400995 |
On Remaining Issue of Uplink Coverage Enhancement |
Apple |
| R1-2401096 |
Maintenance of NR NTN enhancements |
NTT DOCOMO, INC. |
| R1-2401167 |
Maintenance on coverage enhancement for NR NTN |
Sharp |
| R1-2401377 |
Maintenance of coverage enhancement for NR NTN |
Huawei, HiSilicon |
| R1-2401422 |
Maintenance on NR NTN enhancements |
Qualcomm Incorporated |
| R1-2401498 |
Summary #1 on 8.10 Coverage enhancement for NR NTN |
Moderator (NTT DOCOMO) |
| R1-2401499 |
Summary #2 on 8.10 Coverage enhancement for NR NTN |
Moderator (NTT DOCOMO) |
| R1-2401535 |
Moderator summary #1 on remaining issues for RACH-less handover |
Moderator (Samsung) |
| R1-2401537 |
FL Summary #1: Maintenance on Network verified UE location for NR NTN |
Moderator (Thales) |
| R1-2401538 |
FL Summary #2: Maintenance on Network verified UE location for NR NTN |
Moderator (Thales) |
| R1-2401539 |
FL Summary #3: Maintenance on Network verified UE location for NR NTN |
Moderator (Thales) |
| R1-2401540 |
Discussion on FR2-NTN aspects at RAN1#116, first round |
Moderator (Nokia) |
| R1-2401609 |
Moderator summary of Reply LS to R1-2400009 (LS on RAN2 agreements for satellite switch with resync) |
Moderator (Apple) |
| R1-2401610 |
Draft Reply LS on Satellite Switch with Resync |
Moderator (Apple) |
| R1-2401669 |
Discussion on FR2-NTN aspects at RAN1#116, second round |
Moderator (Nokia) |
| R1-2401748 |
Reply LS on Satellite Switch with Resync |
Moderator (Apple) |
| R1-2401764 |
Session notes for 8.10 (Maintenance on NR NTN enhancements) |
Ad-Hoc Chair (Huawei) |
| R1-2401813 |
DRAFT Reply LS on UE capability to support DMRS bundling for GSO and NGSO |
Ericsson |
| R1-2401814 |
Reply LS on UE capability to support DMRS bundling for GSO and NGSO |
RAN1, Ericsson |
| R1-2401846 |
Discussion on FR2-NTN aspects at RAN1#116, third round |
Moderator (Nokia) |
| 8.11 |
Maintenance on other Rel-18 work items |
|
| R1-2400041 |
Draft CR for timing relaxation related spec for eRedCap in TS38213 |
Spreadtrum Communications |
| R1-2400042 |
Draft CR for MBS reception related spec for eRedCap in TS38213 |
Spreadtrum Communications |
| R1-2400043 |
Clarification on remaining issues for eRedCap |
Spreadtrum Communications |
| R1-2400158 |
Discussion on the remaining ambiguities with type 2 CG-PUSCH |
New H3C Technologies Co., Ltd. |
| R1-2400225 |
Maintenance on enhanced reduced capability NR devices |
vivo |
| R1-2400294 |
Draft CR on interleaved VRB-to-PRB mapping in initial BWP |
ZTE |
| R1-2400295 |
Draft CR on PDSCH resource mapping and DMRS reception |
ZTE |
| R1-2400296 |
Draft CR on PDCCH monitoring for dedicated spectrum less than 5MHz. |
ZTE |
| R1-2400297 |
Draft CR on CORESET 0 configuration |
ZTE |
| R1-2400312 |
Draft CR on FDM reception of unicast and multicast PDSCH in RRC_INACTIVE state |
CMCC |
| R1-2400313 |
Draft CR on MCCH change notification of multicast reception in RRC_INACTIVE state |
CMCC |
| R1-2400407 |
Correction on BWP operation without restriction Option B-1-2 |
CATT |
| R1-2400483 |
Discussion on RedCap MBS TEI issues |
ZTE, Sanechips |
| R1-2400484 |
Corrections on MBS for Redcap |
ZTE, Sanechips |
| R1-2400533 |
Discussion on remaining issues for eRedCap UEs |
xiaomi |
| R1-2400594 |
DraftCR on CG-PUSCH grant validation |
OPPO |
| R1-2400595 |
Draft CR on time-domain resource allocation for multi-PUSCH CG configuration |
OPPO |
| R1-2400675 |
On TEI for HARQ-ACK MUX on PUSCH |
Ericsson |
| R1-2400710 |
Remaining issues on multiplexing HARQ-ACK in a PUSCH with repetitions |
Samsung |
| R1-2400798 |
NCD-SSB time offset restriction in TDD for non-RedCap UEs |
Ericsson |
| R1-2400870 |
Alignment for Rel-18 RedCap |
NEC |
| R1-2400952 |
Removal Bandwidth Part without Restriction UE type B-1-2 |
Nokia, Nokia Shanghai Bell |
| R1-2401097 |
Maintenence on further UE complexity reduction for eRedCap |
NTT DOCOMO, INC. |
| R1-2401098 |
Remaining issues on UTO-UCI indication for XR |
NTT DOCOMO, INC. |
| R1-2401099 |
Draft CR on UTO-UCI indication for same CG configuration |
NTT DOCOMO, INC. |
| R1-2401100 |
Maintenance on MBS for RedCap |
NTT DOCOMO, INC. |
| R1-2401199 |
Correction for SPS PDSCH regarding eRedCap |
ASUSTeK |
| R1-2401245 |
NR support for below 5 MHz BW |
Nokia Nokia, Nokia Shanghai Bell |
| R1-2401343 |
Correction of RRC parameter names for XR in TS 38.212 |
Nokia, Nokia Shanghai Bell |
| R1-2401344 |
Correction of RRC parameter names for XR in TS 38.213 |
Nokia, Nokia Shanghai Bell |
| R1-2401345 |
Correction of RRC parameter names for XR in TS 38.214 |
Nokia, Nokia Shanghai Bell |
| R1-2401385 |
Maintenance on Rel-18 RedCap |
Huawei, HiSilicon |
| R1-2401386 |
Correction for CORESET#0 in dedicated spectrum less than 5 MHz |
Huawei, HiSilicon |
| R1-2401423 |
Maintenance on other Rel-18 work items |
Qualcomm Incorporated |
| R1-2401518 |
FL summary #1 for Rel-18 NR eRedCap maintenance |
Moderator (Ericsson) |
| R1-2401519 |
FL summary #2 for Rel-18 NR eRedCap maintenance |
Moderator (Ericsson) |
| R1-2401520 |
FL summary #3 for Rel-18 NR eRedCap maintenance |
Moderator (Ericsson) |
| R1-2401521 |
RAN1 agreements for Rel-18 NR eRedCap |
Rapporteur (Ericsson) |
| R1-2401614 |
Moderator Summary#1 - Maintenance of XR Enhancements |
Moderator (Ericsson) |
| R1-2401615 |
Moderator Summary#2 - Maintenance of XR Enhancements |
Moderator (Ericsson) |
| R1-2401616 |
Moderator Summary#3 - Maintenance of XR Enhancements |
Moderator (Ericsson) |
| R1-2401668 |
Summary of discussion on RedCap MBS TEI issues |
Moderator (ZTE) |
| R1-2401670 |
Intermediate summary of discussion on BWP Without Restriction maintenance |
Moderator (Vodafone) |
| R1-2401671 |
Final summary of discussion on BWP Without Restriction maintenance |
Moderator (Vodafone) |
| R1-2401696 |
FL summary on R18 MBS maintenance |
Moderator (CMCC) |
| R1-2401702 |
Summary of discussion on multiplexing HARQ-ACK in a PUSCH |
Moderator (Samsung) |
| R1-2401706 |
Summary#1 of discussion on enhancements to operate NR on dedicated spectrum less than 5MHz |
Moderator (Lenovo) |
| R1-2401731 |
[Draft] LS on separate CFR introduced in Rel-18 TEI of MBS for RedCap UE applied for eRedCap UE |
ZTE |
| R1-2401732 |
LS on separate CFR introduced in Rel-18 TEI of MBS for RedCap UE applied for eRedCap UE |
RAN1, ZTE |
| R1-2401742 |
[Draft] LS on NCD-SSB time offset for non-RedCap UEs in TDD |
Vodafone |
| R1-2401743 |
LS on NCD-SSB time offset for non-RedCap UEs in TDD |
RAN1, Vodafone |
| R1-2401765 |
Session notes for 8.11 (Maintenance on other Rel-18 work items) |
Ad-Hoc Chair (CMCC) |
| R1-2401774 |
void |
ETSI MCC |
| R1-2401775 |
void |
ETSI MCC |
| R1-2401779 |
Correction of RRC parameter names for UTO-UCI indication |
Moderator (Ericsson), Nokia, Nokia Shanghai Bell |
| R1-2401780 |
Correction of RRC parameter names and applicable configuration for UTO-UCI indication |
Moderator (Ericsson), Nokia, Nokia Shanghai Bell, NTT DOCOMO INC. |
| R1-2401781 |
Correction of RRC parameter names and Multi-PUSCH- CG grant validation |
Moderator (Ericsson), Nokia, Nokia Shanghai Bell, OPPO |
| R1-2401796 |
Summary of discussion on RedCap MBS TEI issues |
Moderator (ZTE) |
| R1-2401817 |
CR on FDM reception of unicast and multicast PDSCH in RRC_INACTIVE state |
Moderator (CMCC) |
| R1-2401818 |
Draft CR on PDCCH monitoring for dedicated spectrum less than 5 MHz |
Lenovo, ZTE, Qualcomm, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, Huawei, HiSilicon |
| R1-2401819 |
Draft CR on PDSCH resource mapping for dedicated spectrum less than 5 MHz |
Lenovo, ZTE, Qualcomm, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, Huawei, HiSilicon |
| R1-2401833 |
CR on PDCCH monitoring for dedicated spectrum less than 5 MHz |
Lenovo, ZTE, Qualcomm, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, Huawei, HiSilicon |
| R1-2401834 |
CR on PDSCH resource mapping for dedicated spectrum less than 5 MHz |
Lenovo, ZTE, Qualcomm, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, Huawei, HiSilicon |
| 8.12 |
UE Features |
|
| R1-2401709 |
Updated RAN1 UE features list for Rel-18 NR after RAN1 #116 |
Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2401710 |
Draft LS on updated Rel-18 RAN1 UE features lists for NR after RAN1#116 |
Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2401711 |
LS on Rel-18 RAN1 UE features lists for NR after RAN1#116 |
RAN1, AT&T, NTT DOCOMO |
| R1-2401822 |
Updated RAN1 UE features list for Rel-18 LTE after RAN1#116 |
Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2401823 |
Draft LS on Rel-18 RAN1 UE features list for LTE after RAN1#116 |
Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2401824 |
LS on Rel-18 RAN1 UE features list for LTE after RAN1#116 |
RAN1, AT&T, NTT DOCOMO, INC. |
| 8.12.1 |
UE features for NR MIMO evolution (NR_MIMO_evo_DL_UL) |
|
| R1-2400081 |
Remaining issues of MIMO UE features |
Nokia, Nokia Shanghai Bell |
| R1-2400103 |
UE features for NR MIMO evolution |
Huawei, HiSilicon |
| R1-2400226 |
Remaining issues on UE features for Rel-18 NR MIMO Evolution |
vivo |
| R1-2400277 |
Discussion on UE features for NR MIMO evolution |
ZTE |
| R1-2400314 |
Discussion on UE feature for NR MIMO evolution |
CMCC |
| R1-2400453 |
Discussion on remaining issues on UE features for NR MIMO evolution |
CATT |
| R1-2400518 |
Discussion on UE features for Rel18 MIMO |
Ericsson |
| R1-2400534 |
Discussion on UE features for NR MIMO evolution |
xiaomi |
| R1-2400579 |
UE features for NR MIMO evolution |
OPPO |
| R1-2400714 |
UE features for Rel-18 NR MIMO |
Samsung |
| R1-2400765 |
Discussion on UE features for NR MIMO evolution |
Fujitsu |
| R1-2400996 |
Views on UE features for Rel-18 NR MIMO evolution |
Apple |
| R1-2401101 |
UE features for NR MIMO evolution |
NTT DOCOMO, INC. |
| R1-2401358 |
Summary of UE features for NR MIMO evolution |
Moderator (AT&T) |
| R1-2401424 |
UE features for NR MIMO evolution |
Qualcomm Incorporated |
| R1-2401618 |
Session Notes of AI 8.12.1 |
Ad-Hoc Chair (AT&T) |
| 8.12.2 |
UE features for NR sidelink evolution (NR_SL_enh2) |
|
| R1-2400082 |
Remaining issues of NR sidelink evolution UE features |
Nokia, Nokia Shanghai Bell |
| R1-2400131 |
UE features for NR sidelink evolution |
Huawei, HiSilicon |
| R1-2400227 |
Discussion on Rel-18 sidelink UE features |
vivo |
| R1-2400414 |
Remaining issues on UE features for NR sidelink evolution |
CATT, CICTCI |
| R1-2400535 |
Maintenance on UE features for NR sidelink evolution |
xiaomi |
| R1-2400584 |
UE features list for Rel-18 NR sidelink evolution WI |
OPPO, Huawei, HiSilicon, LG Electronics |
| R1-2400639 |
UE features for NR sidelink evolution |
ZTE, Sanechips |
| R1-2400715 |
UE features for NR sidelink evolution |
Samsung |
| R1-2400997 |
On UE Features for Rel-18 NR Sidelink Evolution |
Apple |
| R1-2401102 |
Discussion on UE features for NR SL evolution |
NTT DOCOMO, INC. |
| R1-2401168 |
Discussion on UE features for Rel-18 NR sidelink evolution |
Sharp |
| R1-2401321 |
UE feature for NR sidelink evolution |
MediaTek Inc. |
| R1-2401425 |
UE Features for Sidelink Evolution |
Qualcomm Incorporated |
| R1-2401511 |
Summary of discussion on UE features for NR sidelink evolution |
Moderator (NTT DOCOMO, INC.) |
| R1-2401640 |
Summary#2 of discussion on UE features for NR sidelink evolution |
Moderator (NTT DOCOMO, INC.) |
| R1-2401712 |
Session Notes of AI 8.12.2 |
Ad-Hoc Chair (NTT DOCOMO, INC.) |
| R1-2401803 |
Summary#3 of discussion on UE features for NR sidelink evolution |
Moderator (NTT DOCOMO, INC.) |
| 8.12.3 |
UE features for expanded and improved NR positioning (NR_pos_enh2) |
|
| R1-2400083 |
Remaining issues of Positioning UE features |
Nokia, Nokia Shanghai Bell |
| R1-2400139 |
UE features for Rel-18 positioning |
Huawei, HiSilicon |
| R1-2400228 |
Discussion on UE features for Rel-18 positioning |
vivo |
| R1-2400375 |
UE features for Rel-18 Positioning |
Intel Corporation |
| R1-2400415 |
Discussion on UE features for expanded and improved NR positioning |
CATT |
| R1-2400536 |
Discussion on UE features for expanded and improved NR positioning |
xiaomi |
| R1-2400585 |
Remaining issues on UE features for expanded and improved NR positioning |
OPPO |
| R1-2400719 |
UE features for expanded and improved NR positioning |
Samsung |
| R1-2401001 |
Views on UE features for expanded and improved NR positioning |
Apple |
| R1-2401074 |
UE features for Rel-18 NR positioning |
ZTE |
| R1-2401103 |
Discussion on UE features for expanded and improved NR positioning |
NTT DOCOMO, INC. |
| R1-2401352 |
UE features for expanded and improved NR positioning |
Ericsson |
| R1-2401359 |
Summary of UE features for expanded and improved NR positioning |
Moderator (AT&T) |
| R1-2401426 |
UE features for expanded and improved NR positioning |
Qualcomm Incorporated |
| R1-2401619 |
Session Notes of AI 8.12.3 |
Ad-Hoc Chair (AT&T) |
| 8.12.4 |
UE features for MC enhancements (NR_MC_enh) |
|
| R1-2400044 |
Remaining issues on UE features for multi-carrier enhancement |
Spreadtrum Communications |
| R1-2400084 |
Remaining issues of MC-enhancements UE features |
Nokia, Nokia Shanghai Bell |
| R1-2400137 |
Discussion on UE features for MC enhancements |
Huawei, HiSilicon |
| R1-2400229 |
Discussion on Rel-18 Multi-carrier enhancements UE features |
vivo |
| R1-2400298 |
Discussion on UE feature for MC enhancements |
ZTE |
| R1-2400451 |
Discussion on UE features for MC enhancements |
CATT |
| R1-2400537 |
Discussion on UE features for MC enhancements |
xiaomi |
| R1-2400597 |
Discussion on UE features for multi-carrier enhancement |
OPPO |
| R1-2400718 |
UE features for multi-carrier enhancements |
Samsung |
| R1-2400998 |
On remaining issues for UE features for Rel-18 MC enhancements |
Apple |
| R1-2401104 |
Discussion on UE features for multi-carrier enhancements |
NTT DOCOMO, INC. |
| R1-2401141 |
UE features for Rel-18 multi-carrier enhancements |
Ericsson |
| R1-2401290 |
On UE feature discussion for Rel-18 multi-carrier enhancement |
MediaTek Inc. |
| R1-2401324 |
Discussion on UE features for MC enhancements |
LG Electronics |
| R1-2401427 |
UE features for MC enhancements |
Qualcomm Incorporated |
| R1-2401512 |
Summary of discussion on UE features for MC enhancements |
Moderator (NTT DOCOMO, INC.) |
| R1-2401641 |
Summary#2 of discussion on UE features for MC enhancements |
Moderator (NTT DOCOMO, INC.) |
| R1-2401713 |
Session Notes of AI 8.12.4 |
Ad-Hoc Chair (NTT DOCOMO, INC.) |
| 8.12.5 |
UE features for other Rel-18 work items (Topics A: NR_redcap_enh, NR_XR_enh, NR_cov_enh2, NR_FR1_lessthan_5MHz_BW, NR_DSS_enh, TEI) |
|
| R1-2400085 |
Remaining issues of UE Features for Other Topics A (eRedCap, XR, CovEnh, sub-5MHz, eDSS, TEI) |
Nokia, Nokia Shanghai Bell |
| R1-2400148 |
UE features for other Rel-18 WIs (Topics A) |
Huawei, HiSilicon |
| R1-2400230 |
Discussion on Rel-18 UE features for eRedCap, XR and CovEnh |
vivo |
| R1-2400299 |
Discussion on UE feature topics A |
ZTE |
| R1-2400315 |
Discussion on UE feature for coverage enhancement |
CMCC |
| R1-2400416 |
UE features for other Rel-18 work items (Topics A) |
CATT |
| R1-2400598 |
Discussion on UE features under Topic A |
OPPO |
| R1-2400676 |
Rel-18 UE features topics set A |
Ericsson |
| R1-2400716 |
UE features for other Rel-18 work items (Topics A) |
Samsung |
| R1-2400825 |
Remaining issues on UE features for coverage enhancement |
Spreadtrum Communications |
| R1-2400974 |
Discussion on UE features for eRedCap |
xiaomi |
| R1-2400999 |
On UE features for Rel-18 work items in Topic A |
Apple |
| R1-2401035 |
Discussion on UE features for further NR coverage enhancement in Rel.18 |
Panasonic |
| R1-2401105 |
Discussion on UE features for Topic A |
NTT DOCOMO, INC. |
| R1-2401169 |
UE features for Further NR Coverage Enhancements |
Sharp |
| R1-2401305 |
UE features for other Rel-18 work items (Topics A) |
MediaTek Inc. |
| R1-2401428 |
UE features for other Rel-18 work items (Topics A) |
Qualcomm Incorporated |
| R1-2401513 |
Summary of discussion on UE features for coverage enhancements |
Moderator (NTT DOCOMO, INC.) |
| R1-2401514 |
Summary of discussion on UE features for eRedCap |
Moderator (NTT DOCOMO, INC.) |
| R1-2401515 |
Summary of discussion on UE features for XR enhancements |
Moderator (NTT DOCOMO, INC.) |
| R1-2401516 |
Summary of discussion on UE features for dedicated spectrum less than 5MHz |
Moderator (NTT DOCOMO, INC.) |
| R1-2401517 |
Summary of discussion on UE features for TEIs |
Moderator (NTT DOCOMO, INC.) |
| R1-2401642 |
Summary#2 of discussion on UE features for coverage enhancements |
Moderator (NTT DOCOMO, INC.) |
| R1-2401643 |
Summary#2 of discussion on UE features for eRedCap |
Moderator (NTT DOCOMO, INC.) |
| R1-2401644 |
Summary#2 of discussion on UE features for XR enhancements |
Moderator (NTT DOCOMO, INC.) |
| R1-2401645 |
Summary#2 of discussion on UE features for dedicated spectrum less than 5MHz |
Moderator (NTT DOCOMO, INC.) |
| R1-2401646 |
Summary#2 of discussion on UE features for TEIs |
Moderator (NTT DOCOMO, INC.) |
| R1-2401714 |
Session Notes of AI 8.12.5 |
Ad-Hoc Chair (NTT DOCOMO, INC.) |
| R1-2401804 |
Summary#3 of discussion on UE features for coverage enhancements |
Moderator (NTT DOCOMO, INC.) |
| R1-2401805 |
Summary#3 of discussion on UE features for eRedCap |
Moderator (NTT DOCOMO, INC.) |
| R1-2401806 |
Summary#3 of discussion on UE features for XR enhancements |
Moderator (NTT DOCOMO, INC.) |
| R1-2401807 |
Summary#3 of discussion on UE features for dedicated spectrum less than 5MHz |
Moderator (NTT DOCOMO, INC.) |
| R1-2401808 |
Summary#3 of discussion on UE features for TEIs |
Moderator (NTT DOCOMO, INC.) |
| 8.12.6 |
UE features for other Rel-18 work items (Topics B: Netw_Energy_NR, NR_Mob_enh2, NR_netcon_repeater, IoT_NTN_enh, NR_NTN_enh, NR_BWP_wor) |
|
| R1-2400086 |
Remaining issues of UE Features for Other Topics B (NES, MobEnh, NCR, IoT-NTN, NR-NTN, BWP_wor) |
Nokia, Nokia Shanghai Bell |
| R1-2400149 |
UE features for other Rel-18 WIs (Topics B) |
Huawei, HiSilicon |
| R1-2400231 |
Discussion on Rel-18 UE features for NES, Mobility Enh and NR NTN |
vivo |
| R1-2400354 |
Discussion on UE features for Rel-18 Topic-B |
ZTE |
| R1-2400417 |
UE features for other Rel-18 work items (Topics B) |
CATT |
| R1-2400717 |
UE features for other Rel-18 work items (Topics B) |
Samsung |
| R1-2401000 |
On UE features for Rel-18 work items in Topic B |
Apple |
| R1-2401106 |
Discussion on UE features for Mobility, NES, BWP without restriction, and NR-NTN |
NTT DOCOMO, INC. |
| R1-2401142 |
Rel-18 UE features topics set B |
Ericsson |
| R1-2401170 |
UE features for NR NTN |
Sharp |
| R1-2401222 |
Discussion on UE features for other Rel-18 work items (Topics B) |
ETRI |
| R1-2401252 |
Discussion on BWP Without Restriction updates |
Vodafone |
| R1-2401314 |
UE features for other Rel-18 work items (Topics B) |
MediaTek Inc. |
| R1-2401325 |
Discussion on UE features for NES |
LG Electronics |
| R1-2401360 |
Summary of UE features for NR network energy savings |
Moderator (AT&T) |
| R1-2401361 |
Summary of UE features for NR NCR |
Moderator (AT&T) |
| R1-2401362 |
Summary of UE features for NR NTN enhancements |
Moderator (AT&T) |
| R1-2401363 |
Summary of UE features for NR mobility enhancements |
Moderator (AT&T) |
| R1-2401364 |
Summary of UE features for IoT NTN enhancements |
Moderator (AT&T) |
| R1-2401365 |
Summary of UE features for BWP without restriction |
Moderator (AT&T) |
| R1-2401429 |
UE features for other Rel-18 work items (Topics B) |
Qualcomm Incorporated |
| R1-2401471 |
UE features for other Rel-18 work items (Topics B) |
MediaTek Inc. |
| R1-2401620 |
Session Notes of AI 8.12.6 |
Ad-Hoc Chair (AT&T) |
| R1-2401621 |
Summary of UE features for NR ATG |
Moderator (AT&T) |
| 9.1 |
Artificial Intelligence (AI)/Machine Learning (ML) for NR Air Interface (NR_AIML_Air) |
|
| R1-2401430 |
Work plan for Rel-19 WI on AI and ML for NR air interface |
Qualcomm Incorporated |
| R1-2401766 |
Session notes for 9.1 (AI/ML for NR Air Interface) |
Ad-Hoc Chair (CMCC) |
| 9.1.1 |
Specification support for beam management |
|
| R1-2400045 |
Discussion on AIML for beam management |
Spreadtrum Communications |
| R1-2400144 |
Discussion on beam management for AI/ML |
Huawei, HiSilicon |
| R1-2400171 |
AI/ML for beam management |
Ericsson |
| R1-2400232 |
Specification support for beam management |
vivo |
| R1-2400263 |
Discussion on specification support for AI/ML beam management |
ZTE |
| R1-2400274 |
Specification Support for AI/ML beam management |
TCL |
| R1-2400316 |
Discussion on specification support for beam management |
CMCC |
| R1-2400376 |
Specification support for AI/ML for beam management |
Intel Corporation |
| R1-2400392 |
AI/ML based Beam Management |
Google |
| R1-2400418 |
Discussion on AI/ML-based beam management |
CATT |
| R1-2400465 |
Discussion on specification support for beam management |
NEC |
| R1-2400543 |
Specification support for beam management |
xiaomi |
| R1-2400618 |
On specification for AI/ML-based beam management |
OPPO |
| R1-2400683 |
Discussion on AI/ML for beam management |
InterDigital, Inc. |
| R1-2400692 |
Specification support for AI-enabled beam management |
NVIDIA |
| R1-2400720 |
Discussion for supporting AI/ML based beam management |
Samsung |
| R1-2400766 |
Discussion on specification support on AI/ML for beam management |
Fujitsu |
| R1-2400781 |
Discussion on specification support for AI/ML-based beam management |
FUTUREWEI |
| R1-2400793 |
AI/ML for Beam Management |
Nokia, Nokia Shanghai Bell |
| R1-2400830 |
Discussion on specification support for beam management |
Panasonic |
| R1-2400831 |
AI/ML specification support for beam management |
Lenovo |
| R1-2400844 |
Discussions on AI/ML for beam management |
Sony |
| R1-2400895 |
Prediction of untransmitted beams in a UE-side AI-ML model |
Rakuten Mobile, Inc |
| R1-2400907 |
Specification support for beam management |
Fraunhofer HHI, Fraunhofer IIS |
| R1-2400914 |
Discussions on AI/ML for beam management |
LG Electronics |
| R1-2401002 |
Discussion on AI/ML beam management |
Apple |
| R1-2401043 |
Discussion on AI/ML based beam management |
Hyundai Motor Company |
| R1-2401055 |
Discussion on specification support for beam management |
NTPU |
| R1-2401107 |
Discussion on AI/ML for beam management |
NTT DOCOMO, INC. |
| R1-2401134 |
Discussions on AI/ML for beam management |
CAICT |
| R1-2401136 |
Specification support for beam management |
KDDI Corporation |
| R1-2401153 |
Discussion on Specification Support of AI/ML for Beam Management |
Indian Institute of Tech (M), IIT Kanpur |
| R1-2401161 |
Considerations on AI/ML based beam management |
KT Corp. |
| R1-2401171 |
Discussions on specification support for beam management |
Sharp |
| R1-2401179 |
Discussion on support for AI/ML beam management |
ITL |
| R1-2401223 |
Discussion on specification support for beam management |
ETRI |
| R1-2401267 |
Discussion on Specification Support for Beam Management |
CEWiT |
| R1-2401297 |
AI/ML - Specification support for beam management |
MediaTek Inc. |
| R1-2401431 |
Specification support for AI-ML-based beam management |
Qualcomm Incorporated |
| R1-2401475 |
Discussion on specification support for beam management |
NTPU |
| R1-2401596 |
FL summary #0 for AI/ML in management |
Moderator (Samsung) |
| R1-2401597 |
FL summary #1 for AI/ML in management |
Moderator (Samsung) |
| R1-2401598 |
FL summary #2 for AI/ML in management |
Moderator (Samsung) |
| R1-2401599 |
FL summary #3 for AI/ML in management |
Moderator (Samsung) |
| 9.1.2 |
Specification support for positioning accuracy enhancement |
|
| R1-2400101 |
AI/ML for Positioning Accuracy Enhancement |
Ericsson |
| R1-2400145 |
Discussion on positioning accuracy enhancement for AI/ML |
Huawei, HiSilicon |
| R1-2400169 |
Discussion on specification support for AI/ML positioning accuracy enhancement |
ZTE, Pengcheng laboratory |
| R1-2400233 |
Specification support for positioning accuracy enhancement |
vivo |
| R1-2400317 |
Discussion on specification support for positioning accuracy enhancement |
CMCC |
| R1-2400348 |
Discussion on specification support for positioning accuracy enhancement |
TCL |
| R1-2400377 |
Specification support for AI/ML for positioning accuracy enhancement |
Intel Corporation |
| R1-2400393 |
AI/ML based Positioning |
Google |
| R1-2400419 |
Discussion on AI/ML-based positioning accuracy enhancement |
CATT |
| R1-2400469 |
Discussion on specification support for AI/ML based positioning accuracy enhancement |
NEC |
| R1-2400544 |
Discussion on AI/ML-based positioning accuracy enhancement |
xiaomi |
| R1-2400619 |
On specification for AI/ML-based positioning accuracy enhancements |
OPPO |
| R1-2400693 |
Specification support for AI-enabled positioning |
NVIDIA |
| R1-2400721 |
Discussion for supporting AI/ML based positioning accuracy enhancement |
Samsung |
| R1-2400757 |
Discussion on AI/ML-based positioning accuracy enhancement |
CICTCI |
| R1-2400767 |
Discussions on specification support for AI/ML positioning accuracy enhancement |
Fujitsu |
| R1-2400794 |
AI/ML for Positioning Accuracy Enhancement |
Nokia, Nokia Shanghai Bell |
| R1-2400845 |
Discussions on AI/ML for positioning accuracy enhancement |
Sony |
| R1-2400923 |
Specification impacts for Enhanced Positioning |
Lenovo |
| R1-2401003 |
Discussion on Specification support for positioning accuracy enhancement |
Apple |
| R1-2401042 |
Discussion on support for AIML positioning |
InterDigital, Inc. |
| R1-2401056 |
Discussion on Support for Positioning Accuracy Enhancement |
NTPU |
| R1-2401082 |
Discussion on specification support for AI-ML based positioning accuracy enhancement |
Baicells |
| R1-2401108 |
Discussion on specification support for positioning accuracy enhancement |
NTT DOCOMO, INC. |
| R1-2401137 |
Design for AI/ML based positioning |
MediaTek Korea Inc. |
| R1-2401154 |
Discussion on Specification Support of AI/ML for Positioning Accuracy Enhancement |
Indian Institute of Tech (M), IIT Kanpur |
| R1-2401172 |
Discussions on specification support for positioning accuracy enhancements |
Sharp |
| R1-2401198 |
AI/ML positioning accuracy enhancement |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2401268 |
Discussion on specification support for AI/ML Positioning Accuracy enhancement |
CEWiT |
| R1-2401432 |
Specification support for AI-ML-based positioning accuracy enhancement |
Qualcomm Incorporated |
| R1-2401476 |
Discussion on Support for Positioning Accuracy Enhancement |
NTPU |
| R1-2401492 |
Specification support for AI/ML for positioning accuracy enhancement |
Intel Corporation |
| R1-2401544 |
Summary #1 of specification support for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2401545 |
Summary #2 of specification support for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2401546 |
Summary #3 of specification support for positioning accuracy enhancement |
Moderator (Ericsson) |
| R1-2401825 |
Final summary of specification support for positioning accuracy enhancement |
Moderator (Ericsson) |
| 9.1.3 |
Additional study on AI/ML for NR air interface |
|
| R1-2400185 |
Additional study on AI/ML for NR air interface |
Comba |
| 9.1.3.1 |
CSI prediction |
|
| R1-2400046 |
Discussion on AIML for CSI prediction |
Spreadtrum Communications, BUPT |
| R1-2400146 |
Discussion on CSI prediction for AI/ML |
Huawei, HiSilicon |
| R1-2400165 |
AI/ML for CSI prediction |
Ericsson |
| R1-2400234 |
Discussion on CSI prediction |
vivo |
| R1-2400264 |
Discussion on study for AI/ML CSI prediction |
ZTE |
| R1-2400318 |
Discussion on AI/ML for CSI prediction |
CMCC |
| R1-2400379 |
AI/ML for CSI prediction |
Intel Corporation |
| R1-2400394 |
AI/ML based CSI Prediction |
Google |
| R1-2400420 |
Study on AI/ML-based CSI prediction |
CATT |
| R1-2400463 |
Discussion on CSI prediction |
NEC |
| R1-2400545 |
Discussion on one side AI/ML model based CSI prediction |
xiaomi |
| R1-2400620 |
Additional study on AI/ML-based CSI prediction |
OPPO |
| R1-2400656 |
Discussion on AI/ML-based CSI prediction |
China Telecom |
| R1-2400694 |
Additional study on AI-enabled CSI prediction |
NVIDIA |
| R1-2400722 |
Discussion for further study on AI/ML-based CSI prediction |
Samsung |
| R1-2400768 |
Discussion on CSI prediction with AI/ML |
Fujitsu |
| R1-2400795 |
AI/ML for CSI Prediction |
Nokia, Nokia Shanghai Bell |
| R1-2400832 |
On AI/ML for CSI prediction |
Lenovo |
| R1-2400842 |
Discussion on AI/ML for CSI prediction |
SK Telecom |
| R1-2400846 |
Discussions on CSI prediction |
Sony |
| R1-2400896 |
Varying CSI feedback granularity based on channel conditions |
Rakuten Mobile, Inc |
| R1-2400908 |
Discussion on AI/ML-based CSI prediction |
InterDigital, Inc. |
| R1-2400915 |
Study on CSI prediction |
LG Electronics |
| R1-2401004 |
Discussion on AI based CSI prediction |
Apple |
| R1-2401036 |
Discussion on AI/ML for CSI prediction |
Panasonic |
| R1-2401057 |
Discussion on CSI Prediction under AI/ML for NR Air-Interface |
NTPU |
| R1-2401109 |
Discussion on the AI/ML for CSI prediction |
NTT DOCOMO, INC. |
| R1-2401151 |
Discussion on study of AI/ML for CSI prediction |
IIT Kanpur, Indian Institute of Tech (M) |
| R1-2401173 |
Discussions on CSI prediction |
Sharp |
| R1-2401269 |
Discussion on AI/ML for CSI Prediction |
CEWiT |
| R1-2401303 |
CSI Prediction |
MediaTek Inc. |
| R1-2401367 |
Discussion on AI/ML for CSI prediction |
AT&T |
| R1-2401433 |
Additional study on CSI prediction |
Qualcomm Incorporated |
| R1-2401477 |
Discussion on CSI Prediction under AI/ML for NR Air-Interface |
NTPU |
| R1-2401584 |
Summary #1 of CSI prediction |
Moderator (LG Electronics) |
| R1-2401585 |
Summary #2 of CSI prediction |
Moderator (LG Electronics) |
| R1-2401586 |
Summary #3 of CSI prediction |
Moderator (LG Electronics) |
| R1-2401587 |
Summary #4 of CSI prediction |
Moderator (LG Electronics) |
| R1-2401588 |
Summary #5 of CSI prediction |
Moderator (LG Electronics) |
| 9.1.3.2 |
CSI compression |
|
| R1-2400047 |
Discussion on AIML for CSI compression |
Spreadtrum Communications, BUPT |
| R1-2400095 |
Discussion on potential performance enhancements/overhead reduction with AI/ML-based CSI feedback compression |
FUTUREWEI |
| R1-2400150 |
Discussion on CSI compression for AI/ML |
Huawei, HiSilicon |
| R1-2400166 |
AI/ML for CSI compression |
Ericsson |
| R1-2400235 |
Discussion on CSI compression |
vivo |
| R1-2400265 |
Discussion on study for AI/ML CSI compression |
ZTE |
| R1-2400319 |
Discussion on AI/ML for CSI compression |
CMCC |
| R1-2400378 |
AI/ML for CSI compression |
Intel Corporation |
| R1-2400395 |
AI/ML based CSI Compression |
Google |
| R1-2400421 |
Study on AI/ML-based CSI compression |
CATT |
| R1-2400464 |
Discussion on CSI compression |
NEC |
| R1-2400501 |
Discussion on AI/ML for CSI compression |
Comba |
| R1-2400511 |
Discussions on the remaining issues for other aspects of AI/ML for CSI compression |
TCL |
| R1-2400546 |
Discussion on two-sided AI/ML model based CSI compression |
xiaomi |
| R1-2400621 |
Additional study on AI/ML-based CSI compression |
OPPO |
| R1-2400653 |
Discussion on CSI compression for AI/ML |
BJTU |
| R1-2400657 |
Discussion on AI/ML-based CSI compression |
China Telecom |
| R1-2400695 |
Additional study on AI-enabled CSI compression |
NVIDIA |
| R1-2400723 |
Discussion for further study on AI/ML-based CSI compression |
Samsung |
| R1-2400769 |
Discussion on CSI compression with AI/ML |
Fujitsu |
| R1-2400796 |
AI/ML for CSI Compression |
Nokia, Nokia Shanghai Bell |
| R1-2400833 |
On AI/ML for CSI compression |
Lenovo |
| R1-2400847 |
Discussions on CSI compression |
Sony |
| R1-2400909 |
Discussion on AI/ML-based CSI compression |
InterDigital, Inc. |
| R1-2400916 |
Study on CSI compression |
LG Electronics |
| R1-2401005 |
Discussion on AI based CSI compression |
Apple |
| R1-2401037 |
Discussion on AI/ML for CSI compression |
Panasonic |
| R1-2401058 |
Discussion on AI/ML-based CSI compression |
NTPU |
| R1-2401110 |
Discussion on the AI/ML for CSI compression |
NTT DOCOMO, INC. |
| R1-2401135 |
Discussions on AI/ML for CSI feedback |
CAICT |
| R1-2401152 |
Discussion on study of AI/ML for CSI compression |
IIT Kanpur, Indian Institute of Tech (M) |
| R1-2401155 |
Discussion on Additional Study of AI/ML for CSI Compression |
Indian Institute of Tech (M), IIT Kanpur |
| R1-2401174 |
Discussions on CSI compression |
Sharp |
| R1-2401224 |
Discussion on AI/ML for CSI compression |
ETRI |
| R1-2401242 |
Discussion on AI/ML for CSI Compression |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2401270 |
Discussion on AI/ML for CSI Compression |
CEWiT |
| R1-2401304 |
CSI Compression |
MediaTek Inc. |
| R1-2401339 |
Discussion on AI/ML based CSI compression |
ITL |
| R1-2401434 |
Additional study on CSI compression |
Qualcomm Incorporated |
| R1-2401478 |
Discussion on AI/ML-based CSI compression |
NTPU |
| R1-2401557 |
Summary#1 for Additional study on AI/ML for NR air interface: CSI compression |
Moderator (Qualcomm) |
| R1-2401558 |
Summary#2 for Additional study on AI/ML for NR air interface: CSI compression |
Moderator (Qualcomm) |
| R1-2401559 |
Summary#3 for Additional study on AI/ML for NR air interface: CSI compression |
Moderator (Qualcomm) |
| R1-2401560 |
Summary#4 for Additional study on AI/ML for NR air interface: CSI compression |
Moderator (Qualcomm) |
| R1-2401561 |
Summary#5 for Additional study on AI/ML for NR air interface: CSI compression |
Moderator (Qualcomm) |
| R1-2401562 |
Summary#6 for Additional study on AI/ML for NR air interface: CSI compression |
Moderator (Qualcomm) |
| R1-2401563 |
Final summary for Additional study on AI/ML for NR air interface: CSI compression |
Moderator (Qualcomm) |
| 9.1.3.3 |
Other aspects of AI/ML model and data |
|
| R1-2400048 |
Discussion on other aspects of AI/ML model and data |
Spreadtrum Communications |
| R1-2400094 |
Discussion on other aspects of AI/ML model and data on AI/ML for NR air-interface |
FUTUREWEI |
| R1-2400147 |
Discussion on other aspects of the additional study for AI/ML |
Huawei, HiSilicon |
| R1-2400172 |
Discussion on other aspects of AI/ML |
Ericsson |
| R1-2400236 |
Other aspects of AI/ML model and data |
vivo |
| R1-2400266 |
Discussion on study for other aspects of AI/ML model and data |
ZTE |
| R1-2400320 |
Discussion on other aspects of AI/ML model and data |
CMCC |
| R1-2400380 |
Other study aspects of AI/ML for air interface |
Intel Corporation |
| R1-2400396 |
AI/ML Model and Data |
Google |
| R1-2400422 |
Study on other aspects of AI/ML model and data |
CATT |
| R1-2400466 |
Discussion on other aspects of AI/ML model and data |
NEC |
| R1-2400514 |
On AI model transfer |
Dell Technologies |
| R1-2400547 |
Further study on AI/ML model and data |
xiaomi |
| R1-2400622 |
Additional study on other aspects of AI/ML model and data |
OPPO |
| R1-2400696 |
Additional study on other aspects of AI model and data |
NVIDIA |
| R1-2400724 |
Discussion for further study on other aspects of AI/ML model and data |
Samsung |
| R1-2400758 |
On other aspects of AI/ML model and data |
CICTCI |
| R1-2400770 |
Discussion on other aspects of AI/ML model and data |
Fujitsu |
| R1-2400780 |
Discussion on other aspects of AI/ML model and data |
Continental Automotive |
| R1-2400797 |
Other Aspects of AI/ML Model and Data |
Nokia, Nokia Shanghai Bell |
| R1-2400834 |
On aspects of AI/ML model and data framework |
Lenovo |
| R1-2400910 |
Discussion on other aspects of AI/ML model and data |
InterDigital, Inc. |
| R1-2401006 |
Discussion on other aspects of AI/ML model and data |
Apple |
| R1-2401038 |
Discussion on other aspects for AI/ML for air interface |
Panasonic |
| R1-2401060 |
Discussion on functionality update, model identification, data collection and model transfer |
NTPU |
| R1-2401111 |
Discussion on other aspects of AI/ML model and data |
NTT DOCOMO, INC. |
| R1-2401138 |
View on AI/ML model and data |
MediaTek Korea Inc. |
| R1-2401175 |
Discussions on other aspects of AI/ML model and data |
Sharp |
| R1-2401225 |
Discussion on other aspects of AI/ML model and data |
ETRI |
| R1-2401366 |
Other Aspects of AI/ML framework |
AT&T |
| R1-2401435 |
Other aspects of AI/ML model and data |
Qualcomm Incorporated |
| R1-2401479 |
Discussion on functionality update, model identification, data collection and model transfer |
NTPU |
| R1-2401569 |
Summary #1 for other aspects of AI/ML model and data |
Moderator (OPPO) |
| R1-2401570 |
Summary #2 for other aspects of AI/ML model and data |
Moderator (OPPO) |
| R1-2401571 |
Summary #3 for other aspects of AI/ML model and data |
Moderator (OPPO) |
| R1-2401572 |
Summary #4 for other aspects of AI/ML model and data |
Moderator (OPPO) |
| R1-2401573 |
Summary #5 for other aspects of AI/ML model and data |
Moderator (OPPO) |
| 9.2 |
NR MIMO Phase 5 (NR_MIMO_Ph5) |
|
| R1-2400725 |
Rel-19 NR MIMO Phase 5: initial rapporteur assessment |
Moderator (Samsung) |
| 9.2.1 |
Enhancements for UE-initiated/event-driven beam management |
|
| R1-2400049 |
Discussion on UE-initiated/event-driven beam management |
Spreadtrum Communications |
| R1-2400100 |
Enhancements for UE-initiated/event-driven beam management |
FUTUREWEI |
| R1-2400104 |
On UE initiated/event-driven beam management |
Huawei, HiSilicon |
| R1-2400161 |
On UE/Event-Driven Beam Management |
InterDigital, Inc. |
| R1-2400194 |
Enhancements for UE-initiated/event-driven beam management |
Lenovo |
| R1-2400204 |
Enhancements for UE-initiated/event-driven beam management |
Transsion Holdings |
| R1-2400237 |
Discussion on UE-initiated/event-driven beam management |
vivo |
| R1-2400278 |
Discussion on enhancements for UE-initiated/event-driven beam management |
ZTE |
| R1-2400321 |
Discussion on enhancements for UE-initiated/event-driven beam management |
CMCC |
| R1-2400381 |
Enhancements for event driven beam management |
Intel Corporation |
| R1-2400428 |
Discussion on enhancements for UE-initiated/event-driven beam management |
CATT |
| R1-2400467 |
Discussion on enhancements for UE-initiated or event-driven beam management |
NEC |
| R1-2400507 |
Enhancements for UE-initiated/event-driven beam management |
MediaTek Inc. |
| R1-2400553 |
Enhancements for UE-initiated/event-driven beam management |
xiaomi |
| R1-2400623 |
Discussions on UE-initiated/event-driven beam management |
OPPO |
| R1-2400726 |
Views on Rel-19 UE-initiated/event-driven beam management enhancements |
Samsung |
| R1-2400771 |
Discussion on enhancements for UE-initiated/event-driven beam management |
Fujitsu |
| R1-2400848 |
Considerations on UE initiated beam management |
Sony |
| R1-2400912 |
Enhancements for UE-initiated beam management |
Ericsson |
| R1-2400917 |
UE-initiated beam management |
LG Electronics |
| R1-2400933 |
Discussions on enhancements for UE-initiated/event-driven beam management |
Ruijie Network Co. Ltd |
| R1-2400938 |
Enhancements to facilitate UE-initiated/event-driven beam management |
Nokia, Nokia Shanghai Bell |
| R1-2400959 |
Enhancements for UE-initiated/Event-Driven Beam Management |
Panasonic |
| R1-2401007 |
Views on UE-initiated/event-driven beam management |
Apple |
| R1-2401044 |
Enhancements for UE-initiated/event-driven beam management |
Sharp |
| R1-2401049 |
Discussion on enhancements for UE-initiated/event-driven beam management |
Hyundai Motor Company |
| R1-2401078 |
Enhancements for UE-initiated/event-driven beam management |
NICT |
| R1-2401112 |
Discussion on enhancements for UE-initiated/event-driven beam management |
NTT DOCOMO, INC. |
| R1-2401187 |
Discussion on UE-initiated/event-driven beam management |
ITRI |
| R1-2401201 |
Discussion on UE initiated beam management |
ASUSTeK |
| R1-2401226 |
Enhancements for UE-initiated/event-driven beam management |
ETRI |
| R1-2401243 |
Views on enhancements for UE-initiated/event-driven beam management |
KDDI Corporation |
| R1-2401256 |
Discussion on enhancements for UE-initiated or event-driven beam management |
Google |
| R1-2401271 |
Enhancements for UE-initiated/event-driven beam management |
CEWiT |
| R1-2401436 |
UE-initiated/event-driven beam management |
Qualcomm Incorporated |
| R1-2401469 |
Enhancements for event driven beam management |
Intel Corporation |
| R1-2401625 |
Moderator Summary #1 on UE-initiated/event-driven beam management |
Moderator (ZTE) |
| R1-2401681 |
Moderator Summary #2 on UE-initiated/event-driven beam management |
Moderator (ZTE) |
| R1-2401787 |
Moderator Summary #3 on UE-initiated/event-driven beam management |
Moderator (ZTE) |
| 9.2.2 |
CSI enhancements |
|
| R1-2400050 |
Discussion on CSI enhancements |
Spreadtrum Communications |
| R1-2400105 |
On 128 CSI-RS ports and UE reporting enhancement |
Huawei, HiSilicon |
| R1-2400162 |
On Extension of CSI Ports |
InterDigital, Inc. |
| R1-2400195 |
Discussion on CSI enhancements |
Lenovo |
| R1-2400205 |
Discussion on CSI enhancement for 128 CSI-RS ports |
Transsion Holdings |
| R1-2400238 |
Discussion on Rel-19 CSI enhancements |
vivo |
| R1-2400279 |
Discussion on CSI enhancements |
ZTE |
| R1-2400322 |
Discussion on CSI enhancements |
CMCC |
| R1-2400382 |
CSI enhancements for MIMO |
Intel Corporation |
| R1-2400397 |
CSI Enhancement for NR MIMO |
Google |
| R1-2400429 |
Discussion on CSI enhancements in Rel-19 |
CATT |
| R1-2400471 |
Discussion on CSI enhancements |
NEC |
| R1-2400508 |
CSI enhancements to support up to 128 CSI-RS ports |
MediaTek Inc. |
| R1-2400512 |
CSI enhancements |
TCL |
| R1-2400522 |
Discussion on CSI enhancements |
Honor |
| R1-2400554 |
Discussion on CSI enhancement for larger scale transmit antenna ports and CJT |
xiaomi |
| R1-2400624 |
CSI enhancements for Rel-19 MIMO |
OPPO |
| R1-2400658 |
Discussion on CSI enhancement for R19 MIMO evolution |
China Telecom |
| R1-2400727 |
Moderator summary on Rel-19 CSI enhancements |
Moderator (Samsung) |
| R1-2400728 |
Views on Rel-19 CSI enhancements |
Samsung |
| R1-2400753 |
CSI enhancements for large antenna arrays and CJT |
Ericsson |
| R1-2400772 |
Discussion on Rel-19 CSI enhancements |
Fujitsu |
| R1-2400817 |
Overview of CSI Enhancements for NR MIMO Evolution |
Kyocera |
| R1-2400849 |
Views on CSI enhancements |
Sony |
| R1-2400918 |
Discussions on CSI enhancements |
LG Electronics |
| R1-2400939 |
CSI enhancement for NR MIMO Phase 5 |
Nokia, Nokia Shanghai Bell |
| R1-2400957 |
UE Reporting Enhancement for CJT |
Panasonic |
| R1-2401008 |
Views on R19 MIMO CSI enhancement |
Apple |
| R1-2401045 |
CSI enhancements |
Sharp |
| R1-2401113 |
Discussion on CSI enhancements |
NTT DOCOMO, INC. |
| R1-2401244 |
CSI enhancements for Rel.19 MIMO |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2401254 |
Discussion on CSI enhancements |
KDDI Corporation |
| R1-2401272 |
Discussion on Type-II codebook refinement for 128 port CSI-RS |
CEWiT |
| R1-2401357 |
Views on CSI Enhancements for MIMO Phase 5 |
AT&T |
| R1-2401437 |
CSI enhancements for up to 128 ports and UE-assisted CJT with non-ideal TRP synchronization |
Qualcomm Incorporated |
| R1-2401480 |
Overview of CSI Enhancements for NR MIMO Evolution |
Kyocera |
| R1-2401574 |
Moderator Summary for Monday offline session on Rel-19 CSI enhancements |
Moderator (Samsung) |
| R1-2401649 |
Moderator Summary for Tuesday offline session on Rel-19 CSI enhancements |
Moderator (Samsung) |
| R1-2401650 |
Moderator Summary#2 on Rel-19 CSI enhancements: ROUND 2 |
Moderator (Samsung) |
| R1-2401723 |
Moderator Summary for Thursday offline session on Rel-19 CSI enhancements |
Moderator (Samsung) |
| R1-2401724 |
Moderator Summary#3 on Rel-19 CSI enhancements: ROUND 3 |
Moderator (Samsung) |
| 9.2.3 |
Support for 3-antenna-port codebook-based transmissions |
|
| R1-2400051 |
Discussion on 3-antenna-port codebook-based transmissions |
Spreadtrum Communications |
| R1-2400106 |
On codebook for 3-antenna-port UL transmission |
Huawei, HiSilicon |
| R1-2400163 |
On Support of CB-based UL for 3TX UE |
InterDigital, Inc. |
| R1-2400196 |
Support for 3-antenna-port codebook-based transmissions |
Lenovo |
| R1-2400206 |
Support for 3-antenna-port codebook-based transmissions |
Transsion Holdings |
| R1-2400239 |
Discussion on 3-antenna-port codebook-based uplink transmissions |
vivo |
| R1-2400280 |
Discussion on 3-antenna-port codebook-based transmissions |
ZTE |
| R1-2400323 |
Discussion on support for 3-antenna-port codebook-based transmissions |
CMCC |
| R1-2400383 |
Support for 3Tx UL MIMO |
Intel Corporation |
| R1-2400398 |
Uplink 3 Port Codebook based Transmission |
Google |
| R1-2400430 |
Discussion on 3-antenna-port codebook-based transmissions |
CATT |
| R1-2400472 |
Discussion on 3-antenna-port codebook-based transmissions |
NEC |
| R1-2400509 |
Support for 3-antenna-port codebook-based transmissions |
MediaTek Inc. |
| R1-2400513 |
Support for 3-antenna-port codebook-based transmissions |
TCL |
| R1-2400523 |
Discussion on 3-port codebook-based transmissions |
Honor |
| R1-2400555 |
Discussion on the support of 3-antenna-port CB based transmissions |
xiaomi |
| R1-2400625 |
Discussion on 3-antenna-port codebook-based transmissions |
OPPO |
| R1-2400729 |
Views on Rel-19 3-antenna-port codebook-based transmissions |
Samsung |
| R1-2400773 |
Discussion on uplink enhancement for UE with 3Tx |
Fujitsu |
| R1-2400850 |
Considerations on support for 3-antenna-port codebook-based transmissions |
Sony |
| R1-2400919 |
Discussions on 3-antenna-port codebook-based transmissions |
LG Electronics |
| R1-2400940 |
On the support for 3-antenna-port codebook-based transmissions |
Nokia, Nokia Shanghai Bell |
| R1-2401009 |
Views on R19 3Tx codebook based transmission |
Apple |
| R1-2401046 |
Support for 3-antenna-port codebook-based transmission |
Sharp |
| R1-2401077 |
Support for 3 Tx UL transmissions |
Ericsson |
| R1-2401114 |
Discussion on support for 3-antenna-port codebook-based transmissions |
NTT DOCOMO, INC. |
| R1-2401438 |
3 Tx UL MIMO transmissions |
Qualcomm Incorporated |
| R1-2401578 |
FL Summary Support for 3TX CB-based Uplink; First Round |
Moderator (InterDigital, Inc.) |
| R1-2401579 |
FL Summary Support for 3TX CB-based Uplink; Second Round |
Moderator (InterDigital, Inc.) |
| R1-2401580 |
Recommended Direction on 3TX CB-based Uplink in RAN1#116bis |
Moderator (InterDigital, Inc.) |
| R1-2401798 |
FL Summary Support for 3TX CB-based Uplink; Third Round |
Moderator (InterDigital, Inc.) |
| 9.2.4 |
Enhancement for asymmetric DL sTRP/UL mTRP scenarios |
|
| R1-2400052 |
Enhancements for asymmetric DL sTRP/UL mTRP scenarios |
Spreadtrum Communications |
| R1-2400107 |
On power control enhancements for DL sTRP and UL mTRP deployment |
Huawei, HiSilicon |
| R1-2400164 |
On Asymmetric mTRP Deployment |
InterDigital, Inc. |
| R1-2400197 |
Enhancement for asymmetric DL sTRP/UL mTRP scenarios |
Lenovo |
| R1-2400240 |
Discussion on asymmetric DL sTRP/UL mTRP scenarios |
vivo |
| R1-2400267 |
Discussion on asymmetric DL sTRP/UL mTRP scenarios |
TCL |
| R1-2400281 |
Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios |
ZTE, China Telecom |
| R1-2400324 |
Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios |
CMCC |
| R1-2400384 |
Enhancements for asymmetric DL/UL scenarios |
Intel Corporation |
| R1-2400431 |
Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios |
CATT |
| R1-2400468 |
Discussion on enhancements for asymmetric DL sTRP and UL mTRP scenarios |
NEC |
| R1-2400510 |
Enhancement for asymmetric DL sTRP/UL mTRP scenarios |
MediaTek Inc. |
| R1-2400521 |
Enhancement for asymmetric DL sTRP UL mTRP scenarios |
Ericsson |
| R1-2400556 |
Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios |
xiaomi |
| R1-2400626 |
Enhancements on asymmetric DL sTRP/UL mTRP scenarios |
OPPO |
| R1-2400659 |
Discussion on enhancements for asymmetric DL sTRP/UL mTRP scenarios |
China Telecom |
| R1-2400730 |
Views on Rel-19 asymmetric DL sTRP/UL mTRP scenarios |
Samsung |
| R1-2400774 |
Discussion on UL-only mTRP operation |
Fujitsu |
| R1-2400851 |
Considerations on enhancement for asymmetric DL sTRP/UL mTRP scenarios |
Sony |
| R1-2400920 |
Discussions on asymmetric DL sTRP/UL mTRP scenarios |
LG Electronics |
| R1-2400941 |
Enhancement for asymmetric DL sTRP/UL mTRP scenarios |
Nokia, Nokia Shanghai Bell |
| R1-2400958 |
Enhancement for Asymmetric DL sTRP/UL mTRP Scenarios |
Panasonic |
| R1-2401010 |
Views on R19 enhancement for asymmetric DL sTRP/UL mTRP |
Apple |
| R1-2401047 |
Enhancement for asymmetric DL sTRP/UL mTRP scenarios |
Sharp |
| R1-2401050 |
Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios |
Hyundai Motor Company |
| R1-2401052 |
Discussion on enhancement for asymmetric DL sTRP/UL mTRP deployment scenarios |
NTPU |
| R1-2401115 |
Discussion on enhancement for asymmetric DL sTRP/UL mTRP scenarios |
NTT DOCOMO, INC. |
| R1-2401257 |
Discussion on enhancement for asymmetric DL sTRP and UL mTRP scenarios |
Google |
| R1-2401439 |
Enhancement for asymmetric DL sTRP and UL mTRP deployment scenarios |
Qualcomm Incorporated |
| R1-2401472 |
Discussion on enhancement for asymmetric DL sTRP/UL mTRP deployment scenarios |
NTPU |
| R1-2401489 |
Summary #1 on Rel-19 asymmetric DL sTRP/UL mTRP |
Moderator (OPPO) |
| R1-2401490 |
Summary #2 on Rel-19 asymmetric DL sTRP/UL mTRP |
Moderator (OPPO) |
| R1-2401491 |
Summary #3 on Rel-19 asymmetric DL sTRP/UL mTRP |
Moderator (OPPO) |
| 9.3 |
Evolution of NR duplex operation: Sub-band full duplex (SBFD) (NR_duplex_evo) |
|
| R1-2400111 |
Workplan for Evolution of NR Duplex Operation |
Huawei, HiSilicon |
| 9.3.1 |
SBFD TX/RX/measurement procedures |
|
| R1-2400053 |
Discussion on SBFD TX/RX/measurement procedures |
Spreadtrum Communications |
| R1-2400108 |
On subband full duplex design |
Huawei, HiSilicon |
| R1-2400154 |
Discussion for SBFD TX/RX/measurement procedures |
New H3C Technologies Co., Ltd. |
| R1-2400177 |
Discussion on SBFD TX/RX/measurement procedures |
Tejas Network Limited |
| R1-2400207 |
Discussion on SBFD operation |
Transsion Holdings |
| R1-2400241 |
Discussion on Rel-19 SBFD operation |
vivo |
| R1-2400269 |
Discussion on SBFD TX/RX/measurement procedures |
TCL |
| R1-2400300 |
Discussion on transmission, reception and measurement procedures for SBFD operation |
ZTE |
| R1-2400325 |
Discussion on SBFD TX/RX/measurement procedures |
CMCC |
| R1-2400432 |
Discussion on SBFD TX/RX/measurement procedures |
CATT |
| R1-2400557 |
Discussion on reception and transmission procedure for SBFD operation |
xiaomi |
| R1-2400606 |
Discussion on SBFD Tx/Rx/measurement procedures |
OPPO |
| R1-2400643 |
SBFD procedures in RRC_CONNECTED mode |
Sharp |
| R1-2400660 |
Discussion on SBFD TX/RX/measurement procedures |
China Telecom |
| R1-2400687 |
Discussion on SBFD TX RX and measurement procedures |
InterDigital, Inc. |
| R1-2400731 |
SBFD operation and procedures |
Samsung |
| R1-2400775 |
Discussion on Tx/Rx/Measurement procedures for SBFD operation |
Fujitsu |
| R1-2400802 |
Discussion on subband non-overlapping full duplex Tx-Rx and measurement operations |
NEC |
| R1-2400826 |
Discussion on SBFD TX/RX/measurement procedures |
Panasonic |
| R1-2400838 |
On SBFD TX/RX/measurement procedures |
Nokia, Nokia Shanghai Bell |
| R1-2400852 |
SBFD operations |
Sony |
| R1-2401011 |
Views on SBFD TX/RX/measurement procedures |
Apple |
| R1-2401081 |
On semi-static indication of SBFD resources |
Google Inc. |
| R1-2401116 |
Discussion on SBFD TX/RX/measurement procedures |
NTT DOCOMO, INC. |
| R1-2401159 |
Considerations on SBFD Tx/Rx/measurement procedure |
KT Corp. |
| R1-2401188 |
Discussion on SBFD TX/RX/measurement procedures |
ITRI |
| R1-2401191 |
Tx Rx procedure for SBFD |
ASUSTeK |
| R1-2401214 |
Discussion on SBFD TX/RX/measurement procedures |
WILUS |
| R1-2401217 |
SBFD TX/RX/measurement procedures |
Ericsson |
| R1-2401227 |
Discussion on SBFD TX/RX/measurement procedures |
ETRI |
| R1-2401249 |
Discussion on SBFD TX/RX/measurement procedures |
LG Electronics |
| R1-2401263 |
Views on sub-band full duplex operations |
Lenovo |
| R1-2401273 |
Discussion on SBFD TX/RX/ measurement procedures |
CEWiT |
| R1-2401294 |
Discussion on SBFD TX/RX/measurement procedures |
MediaTek Inc. |
| R1-2401440 |
SBFD Transmission, Reception and Measurement Procedures |
Qualcomm Incorporated |
| R1-2401652 |
Summary #1 of SBFD TX/RX/measurement procedures |
Moderator (CATT) |
| R1-2401653 |
Summary #2 of SBFD TX/RX/measurement procedures |
Moderator (CATT) |
| R1-2401654 |
Summary #3 of SBFD TX/RX/measurement procedures |
Moderator (CATT) |
| 9.3.2 |
SBFD random access operation |
|
| R1-2400054 |
Discussion on SBFD random access operation |
Spreadtrum Communications, BUPT |
| R1-2400109 |
On subband full duplex random access operation |
Huawei, HiSilicon |
| R1-2400153 |
Discussion for SBFD random access operation |
New H3C Technologies Co., Ltd. |
| R1-2400178 |
Discussion on SBFD Random Access Operation |
Tejas Network Limited |
| R1-2400242 |
Discussion on random access for Rel-19 SBFD |
vivo |
| R1-2400270 |
Discussion on SBFD random access operation |
TCL |
| R1-2400301 |
Discussion on SBFD random access operation |
ZTE |
| R1-2400326 |
Discussion on SBFD random access operation |
CMCC |
| R1-2400433 |
Discussion on SBFD random access operation |
CATT |
| R1-2400558 |
Discussion on SBFD random access operation |
xiaomi |
| R1-2400607 |
Discussion on SBFD random access operation |
OPPO |
| R1-2400651 |
Random access in SBFD symbols |
Sharp |
| R1-2400661 |
Discussion on SBFD random access operation |
China Telecom |
| R1-2400688 |
Discussion on enhancements for SBFD random access operations |
InterDigital, Inc. |
| R1-2400732 |
Random access on SBFD resources |
Samsung |
| R1-2400803 |
Discussion on random access for subband non-overlapping full duplex |
NEC |
| R1-2400827 |
Discussion on SBFD random access operation |
Panasonic |
| R1-2400839 |
SBFD random access operation |
Nokia, Nokia Shanghai Bell |
| R1-2400853 |
SBFD RACH operations |
Sony |
| R1-2400877 |
Discussion on Random Access for subband non-overlapping full duplex |
SK Telecom |
| R1-2401012 |
Views on SBFD random access operation |
Apple |
| R1-2401084 |
SBFD random access operation |
Lenovo |
| R1-2401117 |
Discussion on SBFD random access operation |
NTT DOCOMO, INC. |
| R1-2401189 |
Discussion on SBFD operation to UE in RRC_IDLE/INACTIVE mode for random access |
ITRI |
| R1-2401192 |
Random access procedure for SBFD |
ASUSTeK |
| R1-2401210 |
Discussion on random access operation on SBFD symbols |
Fujitsu |
| R1-2401215 |
Discussion on SBFD random access operation |
WILUS |
| R1-2401218 |
SBFD Random access operation |
Ericsson |
| R1-2401228 |
SBFD random access operation |
ETRI |
| R1-2401250 |
Discussion on SBFD random access operation |
LG Electronics |
| R1-2401295 |
Discussion on SBFD random access operation |
MediaTek Inc. |
| R1-2401441 |
SBFD Random Access Operation |
Qualcomm Incorporated |
| R1-2401676 |
Summary#1 on SBFD random access operation |
Moderator (CMCC) |
| R1-2401677 |
Summary#2 on SBFD random access operation |
Moderator (CMCC) |
| R1-2401678 |
Summary#3 on SBFD random access operation |
Moderator (CMCC) |
| 9.3.3 |
CLI handling |
|
| R1-2400055 |
Discussion on CLI handling |
Spreadtrum Communications |
| R1-2400110 |
On cross-link interference handling for subband full duplex |
Huawei, HiSilicon |
| R1-2400156 |
Discussion on CLI handling |
New H3C Technologies Co., Ltd. |
| R1-2400179 |
Discussion on SBFD CLI Handling |
Tejas Network Limited |
| R1-2400243 |
Discussion on CLI handling for Rel-19 NR duplex |
vivo |
| R1-2400271 |
Discussion on CLI handling in SBFD/dynamic TDD operation. |
TCL |
| R1-2400302 |
Discussion on CLI handling for Rel-19 duplex operation |
ZTE |
| R1-2400327 |
Discussion on CLI handling |
CMCC |
| R1-2400434 |
Discussion on CLI handling for NR duplex evolution |
CATT |
| R1-2400559 |
Discussion on CLI handling for SBFD operation |
xiaomi |
| R1-2400608 |
CLI handling in NR duplex operation |
OPPO |
| R1-2400689 |
Discussion on CLI handling for SBFD operations |
InterDigital, Inc. |
| R1-2400733 |
Cross-link interference handling for SBFD |
Samsung |
| R1-2400776 |
Discussion on CLI handling for SBFD operation |
Fujitsu |
| R1-2400804 |
CLI handling for NR duplex operation |
NEC |
| R1-2400828 |
Discussion on CLI handling |
Panasonic |
| R1-2400835 |
Cross-link interference management for duplexing evolution |
Lenovo |
| R1-2400840 |
Cross-link interference handling for duplex evolution |
Nokia, Nokia Shanghai Bell |
| R1-2400854 |
CLI handling for SBFD |
Sony |
| R1-2401013 |
Views on CLI handling |
Apple |
| R1-2401118 |
Discussion on CLI handling for sub-band full duplex (SBFD) |
NTT DOCOMO, INC. |
| R1-2401216 |
Discussion on CLI handling for evolution of NR duplex operation |
WILUS |
| R1-2401219 |
CLI handling |
Ericsson |
| R1-2401229 |
Discussion on CLI handling for SBFD operation |
ETRI |
| R1-2401246 |
On the gNB-to-gNB CLI and the UE-to-UE CLI handling |
Google Inc. |
| R1-2401251 |
Discussion on CLI handling |
LG Electronics |
| R1-2401274 |
Discussion on CLI handling |
CEWiT |
| R1-2401296 |
Discussion on CLI handling in SBFD |
MediaTek Inc. |
| R1-2401442 |
Enhancements for CLI handling |
Qualcomm Incorporated |
| R1-2401633 |
Summary #1 of CLI handling |
Moderator (Huawei) |
| R1-2401634 |
Summary #2 of CLI handling |
Moderator (Huawei) |
| R1-2401635 |
Summary #3 of CLI handling |
Moderator (Huawei) |
| 9.4 |
Study on solutions for Ambient IoT (Internet of Things) in NR (FS_Ambient_IoT_solutions) |
|
| R1-2400328 |
Ambient IoT Study Item work plan |
CMCC, Huawei, T-Mobile USA |
| R1-2400783 |
Operator view on Ambient IoT design targets |
T-Mobile USA Inc. |
| R1-2400956 |
LS to SA3 requesting Ambient IoT security requirements |
T-Mobile USA Inc. |
| R1-2401404 |
Skeleton for TR 38.769 "Study on Solutions for Ambient IoT (Internet of Things)" v0.0.1 |
Huawei |
| R1-2401767 |
Session notes for 9.4 (Study on solutions for Ambient IoT in NR) |
Ad-Hoc Chair (Huawei) |
| R1-2401795 |
Skeleton for TR 38.769 "Study on Solutions for Ambient IoT (Internet of Things)" v0.0.1 |
Huawei |
| R1-2401797 |
Editor’s summary for discussion on TR 38.769 skeleton |
Huawei |
| 9.4.1.1 |
Evaluation assumptions and results |
|
| R1-2400056 |
Discussion on evaluation assumptions and results for Ambient IoT |
Spreadtrum Communications |
| R1-2400075 |
Evaluation assumptions and results for Ambient IoT |
Ericsson |
| R1-2400087 |
Discussion on evaluation assumptions and results for Ambient IoT devices |
FUTUREWEI |
| R1-2400113 |
Evaluation assumptions for Ambient IoT |
Huawei, HiSilicon |
| R1-2400244 |
Evaluation methodologies assumptions and results for Ambient IoT |
vivo |
| R1-2400329 |
Discussion on evaluation methodology and assumptions |
CMCC |
| R1-2400361 |
Initial views on Evaluation assumptions and results for Ambient IoT |
Nokia, Nokia Shanghai Bell |
| R1-2400435 |
The evaluation methodology and preliminary results of Ambient IoT |
CATT |
| R1-2400486 |
Discussion on Ambient IoT evaluations |
ZTE, Sanechips |
| R1-2400560 |
Evaluation methodology and assumptions for Ambient IoT |
xiaomi |
| R1-2400609 |
Discussion on evaluation assumptions and results for A-IoT |
OPPO |
| R1-2400662 |
Discussion on evaluation assumptions and results for Ambient IoT |
China Telecom |
| R1-2400734 |
Considerations for evaluation assumptions and results |
Samsung |
| R1-2400805 |
Discussion on ambient IoT evaluation framework |
NEC |
| R1-2400855 |
Evaluation assumptions for Ambient IoT |
Sony |
| R1-2400885 |
Discussion on the evaluation assumptions for Ambient IoT devices |
Lenovo |
| R1-2400924 |
The Evaluation on Ambient IoT in NR |
Comba |
| R1-2400942 |
Considerations for evaluation assumptions and results |
Semtech Neuchatel SA |
| R1-2401014 |
Views on evaluation assumptions and link budget analysis for AIoT |
Apple |
| R1-2401156 |
Discussion on Evaluation Assumptions and Results for Ambient IoT |
Indian Institute of Tech (M), IIT Kanpur |
| R1-2401180 |
Evaluation assumptions for Ambient IoT |
InterDigital, Inc. |
| R1-2401306 |
On evaluation assumptions and results for A-IoT |
MediaTek Inc. |
| R1-2401326 |
Discussion on Ambient IoT evaluation |
LG Electronics |
| R1-2401443 |
Evaluation Assumptions and Results |
Qualcomm Incorporated |
| R1-2401647 |
FL summary #1 for Ambient IoT evaluation |
Moderator (CMCC) |
| R1-2401735 |
FL summary #2 for Ambient IoT evaluation |
Moderator (CMCC) |
| R1-2401874 |
FL summary (final) for Ambient IoT evaluation |
Moderator (CMCC) |
| 9.4.1.2 |
Ambient IoT device architectures |
|
| R1-2400057 |
Discussion on Ambient IoT device architectures |
Spreadtrum Communications |
| R1-2400076 |
Ambient IoT device architectures |
Ericsson |
| R1-2400088 |
Discussion on Ambient IoT device architectures |
FUTUREWEI |
| R1-2400114 |
Ultra low power device architecture for Ambient IoT |
Huawei, HiSilicon |
| R1-2400187 |
Discussion on ambient IoT architecture |
TCL |
| R1-2400245 |
Discussion on Ambient IoT Device architectures |
vivo |
| R1-2400330 |
Discussion on Ambient IoT device architectures |
CMCC |
| R1-2400362 |
Initial views on Ambient IoT device architectures |
Nokia, Nokia Shanghai Bell |
| R1-2400436 |
Study of the Ambient IoT devices architecture |
CATT |
| R1-2400487 |
Discussion on Ambient IoT device architectures |
ZTE, Sanechips |
| R1-2400524 |
Discussion on Ambient IoT device architectures |
Honor |
| R1-2400561 |
Discussion on ambient IoT device architectures |
xiaomi |
| R1-2400610 |
Discussion on device architecture for A-IoT device |
OPPO |
| R1-2400735 |
Considerations for Ambient-IoT device architectures |
Samsung |
| R1-2400856 |
Ambient IoT device architectures |
Sony |
| R1-2400887 |
Discussion on the Ambient IoT device architectures |
Lenovo |
| R1-2400926 |
Ambient IoT device architectures |
Comba |
| R1-2401015 |
Views on device architecture for AIoT |
Apple |
| R1-2401065 |
Ambient IoT device architectures |
China Unicom |
| R1-2401182 |
Device architectures for Ambient IoT |
InterDigital, Inc. |
| R1-2401264 |
Discussion on Ambient IoT device architectures |
IIT Kanpur, Indian Institute of Tech (M) |
| R1-2401275 |
Discussion on Ambient IoT device architectures |
CEWiT |
| R1-2401307 |
On Ambient IoT device architectures |
MediaTek Inc. |
| R1-2401327 |
Discussion on Ambient IoT device architectures |
LG Electronics |
| R1-2401403 |
Discussion on Ambient IoT device architectures |
Sequans Communications |
| R1-2401444 |
Ambient IoT Device Architecture |
Qualcomm Incorporated |
| R1-2401682 |
FL Summary#1 for 9.4.1.2 Ambient IoT Device Architecture |
Moderator (Qualcomm) |
| R1-2401703 |
FL Summary#2 for 9.4.1.2 Ambient IoT Device Architecture |
Moderator (Qualcomm) |
| R1-2401704 |
FL Summary#3 for 9.4.1.2 Ambient IoT Device Architecture |
Moderator (Qualcomm) |
| R1-2401835 |
FL Summary#4 for 9.4.1.2 Ambient IoT Device Architecture |
Moderator (Qualcomm) |
| 9.4.2.1 |
General aspects of physical layer design |
|
| R1-2400058 |
Discussion on general aspects of physical layer design for Ambient IoT |
Spreadtrum Communications |
| R1-2400077 |
General aspects of physical layer design for Ambient IoT |
Ericsson |
| R1-2400089 |
Discussion on physical layer design for Ambient IoT devices |
FUTUREWEI |
| R1-2400115 |
On general aspects of physical layer design for Ambient IoT |
Huawei, HiSilicon |
| R1-2400246 |
Discussion on General Aspects of Physical Layer Design |
vivo |
| R1-2400331 |
Discussion on general aspects of Ambient IOT physical layer design |
CMCC |
| R1-2400363 |
Initial views on General aspects of physical layer design for Ambient IoT |
Nokia, Nokia Shanghai Bell |
| R1-2400385 |
Optimal Training Sequence for Backscattering Tag |
BJTU |
| R1-2400437 |
Discussion on general aspects of physical layer design |
CATT |
| R1-2400459 |
Discussion on general aspects of ambient IoT physical layer design |
NEC |
| R1-2400488 |
Discussion on general aspects of physical layer design for Ambient IoT |
ZTE, Sanechips |
| R1-2400562 |
Discussion on physical layer design of Ambient IoT |
xiaomi |
| R1-2400611 |
Discussion on general aspects of physical layer design of A-IoT communication |
OPPO |
| R1-2400630 |
Discussion on general aspects of physical layer design |
Sharp |
| R1-2400663 |
Discussion on general aspects of physical layer design for Ambient IoT |
China Telecom |
| R1-2400736 |
Discussion on general aspects of Ambient IoT |
Samsung |
| R1-2400755 |
Modulation Comparison for AIoT |
Wiliot Ltd. |
| R1-2400756 |
On General Physical Layer Design Considerations for Ambient IoT Applications |
Lekha Wireless Solutions |
| R1-2400777 |
Consideration on general aspects of physical layer |
Fujitsu |
| R1-2400857 |
General aspects of physical layer design for Ambient IoT |
Sony |
| R1-2400872 |
Discussions on general aspects for A-IoT |
Intel Corporation |
| R1-2400888 |
Discussion on the Physical layer design for Ambient IoT devices |
Lenovo |
| R1-2400934 |
Discussions on general aspects of physical layer design for Ambient IoT |
Ruijie Network Co. Ltd |
| R1-2401016 |
Views on general physical layer design aspects for AIoT |
Apple |
| R1-2401034 |
General aspects of physical layer design for Ambient IoT |
Panasonic |
| R1-2401119 |
Study on general aspects of physical layer design for Ambient IoT |
NTT DOCOMO, INC. |
| R1-2401160 |
Views on physical layer design |
Comba |
| R1-2401183 |
Physical layer design for Ambient IoT |
InterDigital, Inc. |
| R1-2401230 |
Discussion on general aspects of physical layer design for ambient IoT |
ETRI |
| R1-2401258 |
Discussion on general aspects of physical layer design |
Google |
| R1-2401265 |
Discussion on General aspects of physical layer design |
IIT Kanpur, Indian Institute of Tech (M) |
| R1-2401276 |
Discussion on General aspects of physical layer design |
CEWiT |
| R1-2401308 |
On general aspects of physical layer design for A-IoT |
MediaTek Inc. |
| R1-2401328 |
General aspects of Ambient IoT physical layer design |
LG Electronics |
| R1-2401350 |
General aspects of physical layer design |
Nordic Semiconductor ASA |
| R1-2401405 |
Discussion on general aspects of physical layer design for Ambient IoT |
Sequans Communications |
| R1-2401445 |
General aspects of physical layer design |
Qualcomm Incorporated |
| R1-2401464 |
General aspects of physical layer design for Ambient IoT |
ITL |
| R1-2401493 |
Discussion on general aspects of physical layer design for Ambient IoT |
ZTE, Sanechips |
| R1-2401567 |
Feature Lead Summary for 9.4.2.1: “Ambient IoT – General aspects of physical layer design” #1 |
Moderator (Huawei) |
| R1-2401568 |
Feature Lead Summary for 9.4.2.1: “Ambient IoT – General aspects of physical layer design” #2 |
Moderator (Huawei) |
| R1-2401851 |
Feature Lead Summary for 9.4.2.1: “Ambient IoT – General aspects of physical layer design” – #3 |
Moderator (Huawei) |
| 9.4.2.2 |
Frame structure and timing aspects |
|
| R1-2400059 |
Discussion on frame structure and timing aspects for Ambient IoT |
Spreadtrum Communications |
| R1-2400078 |
Frame structure and timing aspects for Ambient IoT |
Ericsson |
| R1-2400090 |
Discussion on frame structure and timing aspects for Ambient IoT devices |
FUTUREWEI |
| R1-2400116 |
On frame structure and timing aspects of Ambient IoT |
Huawei, HiSilicon |
| R1-2400200 |
Discussion on frame structure and timing aspects for ambient IoT |
Lenovo |
| R1-2400247 |
Discussion on Frame structure, random access, scheduling and timing aspects |
vivo |
| R1-2400305 |
Discussion on frame structure and timing aspects for Ambient IoT |
TCL |
| R1-2400332 |
Discussion on frame structure and timing aspects for Ambient IOT |
CMCC |
| R1-2400364 |
Initial views on Frame structure and timing aspects for Ambient IoT |
Nokia, Nokia Shanghai Bell |
| R1-2400373 |
Discussions on frame structure and timing aspects for A-IoT |
Intel Corporation |
| R1-2400438 |
Study of Frame structure and timing aspects for Ambient IoT |
CATT |
| R1-2400460 |
Discussion on frame structure and timing for ambient IoT |
NEC |
| R1-2400489 |
Discussion on frame structure and physical layer procedure for Ambient IoT |
ZTE, Sanechips |
| R1-2400563 |
Discussion on frame structure and timing aspects for Ambient IoT |
xiaomi |
| R1-2400612 |
Initial considerations on frame structure and timing aspects of A-IoT communication |
OPPO |
| R1-2400631 |
Discussion on frame structure and timing aspects |
Sharp |
| R1-2400664 |
Discussion on frame structure and timing aspects for Ambient IoT |
China Telecom |
| R1-2400737 |
Considerations for frame structure and timing aspects |
Samsung |
| R1-2400778 |
Discussion on frame structure and timing |
Fujitsu |
| R1-2400784 |
Discussion on frame structure and timing aspects for Ambient IoT |
BUPT |
| R1-2400799 |
The frame structure consideration for Ambient IoT |
Comba |
| R1-2400858 |
Frame structure and timing aspects for Ambient IoT |
Sony |
| R1-2400954 |
Frame structure and timing aspects of Ambient IoT |
InterDigital, Inc. |
| R1-2401017 |
Views on frame structure, synchronization, random access and timing for AIoT |
Apple |
| R1-2401062 |
Discussion on A-IoT Frame Structure and Timing Aspects |
Panasonic |
| R1-2401066 |
Ambient IoT: Frame structure and timing aspects |
China Unicom |
| R1-2401120 |
Study on frame structure and timing aspects for Ambient IoT |
NTT DOCOMO, INC. |
| R1-2401157 |
Discussion on Frame Structure and Timing Aspects for Ambient IoT |
Indian Institute of Tech (M), IIT Kanpur |
| R1-2401231 |
Discussion on frame structure for ambient IoT |
ETRI |
| R1-2401259 |
Discussion on frame structure and timing aspects |
Google |
| R1-2401266 |
Discussion on Frame structure and timing aspects |
IIT Kanpur, Indian Institute of Tech (M) |
| R1-2401277 |
Discussion on Frame structure and timing aspects |
CEWiT |
| R1-2401309 |
On frame structure and timing aspects for A-IoT |
MediaTek Inc. |
| R1-2401329 |
Frame structure and timing aspects for Ambient IoT |
LG Electronics |
| R1-2401402 |
Discussion on frame structure and timing aspects for Ambient IoT |
Sequans Communications |
| R1-2401446 |
Frame structure and timing aspects |
Qualcomm Incorporated |
| R1-2401541 |
FL summary #1 on frame structure and timing aspects for Rel-19 Ambient IoT |
Moderator (vivo) |
| R1-2401789 |
FL summary #2 on frame structure and timing aspects for Rel-19 Ambient IoT |
Moderator (vivo) |
| R1-2401849 |
Final summary on frame structure and timing aspects for Rel-19 Ambient IoT |
Moderator (vivo) |
| 9.4.2.3 |
Downlink and uplink channel/signal aspects |
|
| R1-2400060 |
Discussion on downlink and uplink channel/signal aspects for Ambient IoT |
Spreadtrum Communications |
| R1-2400079 |
Downlink and uplink channel/signal aspects for Ambient IoT |
Ericsson |
| R1-2400091 |
Discussion on DL and UL channel/signal aspects for Ambient IoT devices |
FUTUREWEI |
| R1-2400117 |
Physical channels and signals for Ambient IoT |
Huawei, HiSilicon |
| R1-2400188 |
Discussion on downlink and uplink channel/signal aspects |
TCL |
| R1-2400189 |
Discussion on downlink and uplink channel/signal aspects |
TCL |
| R1-2400201 |
Discussion on downlink and uplink channel/signal aspects for ambient IoT |
Lenovo |
| R1-2400248 |
Discussion on Downlink and uplink channel/signal aspects |
vivo |
| R1-2400333 |
Discussion on downlink and uplink channel/signal aspects |
CMCC |
| R1-2400365 |
Initial views on Downlink and uplink channel/signal aspects for Ambient IoT |
Nokia, Nokia Shanghai Bell |
| R1-2400439 |
DL and UL Physical Channels/signals design in support of Ambient IoT devices |
CATT |
| R1-2400461 |
Discussion on downlink and uplink channel for ambient IoT |
NEC |
| R1-2400490 |
Discussion on downlink and uplink channel and signal for Ambient IoT |
ZTE, Sanechips |
| R1-2400564 |
Discussion on downlink and uplink channel/signal aspects for Ambient IoT |
xiaomi |
| R1-2400613 |
Discussion on downlink and uplink channel/signal aspects for A-IoT |
OPPO |
| R1-2400632 |
Discussion on downlink and uplink channel/signal aspects |
Sharp |
| R1-2400665 |
Discussion on downlink and uplink channel/signal aspects for Ambient IoT |
China Telecom |
| R1-2400738 |
Considerations for downlink and uplink channel/signal aspect |
Samsung |
| R1-2400779 |
Discussion on downlink and uplink channel/signal |
Fujitsu |
| R1-2400800 |
The downlink and uplink channel consideration for Ambient IoT |
Comba |
| R1-2400812 |
Discussion on Downlink and Uplink Channel/Signal Aspects for A-IoT |
EURECOM |
| R1-2400859 |
Downlink and uplink physical channel for Ambient IoT |
Sony |
| R1-2400890 |
Discussion on downlink and uplink channels and signals for A-IoT |
Panasonic |
| R1-2400955 |
Downlink and uplink channels aspects of Ambient IoT |
InterDigital, Inc. |
| R1-2401018 |
Views on DL and UL PHY channels/signals and proximity determination for AIoT |
Apple |
| R1-2401067 |
Ambient IoT: Downlink and uplink channel/signal aspects |
China Unicom |
| R1-2401121 |
Study on downlink and uplink channel/signal aspects for Ambient IoT |
NTT DOCOMO, INC. |
| R1-2401260 |
Discussion on downlink and uplink transmission aspects |
Google |
| R1-2401283 |
Discussion on Downlink and uplink channel/signal aspects |
IIT Kanpur, Indian Institute of Tech (M) |
| R1-2401310 |
On downlink and uplink channel/signal aspects for A-IoT |
MediaTek Inc. |
| R1-2401330 |
Downlink and uplink channel/signal aspects for Ambient IoT |
LG Electronics |
| R1-2401401 |
Discussion on DL and UL channel/signal aspects for Ambient IoT |
Sequans Communications |
| R1-2401447 |
Downlink and uplink channel/signal aspects |
Qualcomm Incorporated |
| R1-2401729 |
Feature lead summary#1 on downlink and uplink channel/signal aspects |
Moderator (Apple) |
| R1-2401799 |
Feature lead summary#2 on downlink and uplink channel/signal aspects |
Moderator (Apple) |
| R1-2401857 |
Final feature lead summary on downlink and uplink channel/signal aspects |
Moderator (Apple) |
| 9.4.2.4 |
Waveform characteristics of carrier-wave provided externally to the Ambient IoT device |
|
| R1-2400061 |
Discussion on waveform characteristics of external carrier-wave for Ambient IoT |
Spreadtrum Communications |
| R1-2400080 |
Waveform characteristics of carrier wave provided externally to the Ambient IoT device |
Ericsson |
| R1-2400092 |
Discussion on external carrier waveform characteristics for Ambient IoT devices |
FUTUREWEI |
| R1-2400118 |
On external carrier wave for backscattering based Ambient IoT device |
Huawei, HiSilicon |
| R1-2400190 |
Discussion on waveform characteristics of external carrier-wave for Ambient IoT |
TCL |
| R1-2400202 |
Discussion on external carrier wave for ambient IoT |
Lenovo |
| R1-2400249 |
Discussion on CW waveform and interference handling at AIoT UL receiver |
vivo |
| R1-2400334 |
Discussion on waveform characteristics of carrier-wave provided externally to the Ambient IoT device |
CMCC |
| R1-2400366 |
Initial views on Waveform characteristics of carrier-wave provided externally to the Ambient IoT device |
Nokia, Nokia Shanghai Bell |
| R1-2400386 |
Backscatter Scheme for Same Frequency Interference Avoidance and Image Interference Suppression |
BJTU |
| R1-2400440 |
Discussion on the waveform characteristics of carrier-wave for the Ambient IoT device |
CATT |
| R1-2400491 |
Discussion on carrier wave for Ambient IoT |
ZTE, Sanechips |
| R1-2400565 |
Discussion on waveform characteristics of carrier-wave |
xiaomi |
| R1-2400614 |
Discussion on Waveform characteristics of carrier-wave provided externally to the A-IoT device |
OPPO |
| R1-2400633 |
Discussion on waveform characteristics of externally provided carrier-wave |
Sharp |
| R1-2400666 |
Discussion on waveform characteristics of carrier-wave provided externally to the Ambient IoT device |
China Telecom |
| R1-2400739 |
Considerations for Waveform characteristics of carrier-wave |
Samsung |
| R1-2400860 |
External carrier wave for Ambient IoT |
Sony |
| R1-2401019 |
Views on carrier waveform and interference handling for AIoT |
Apple |
| R1-2401122 |
Study on waveform characteristics of carrier-wave for Ambient IoT |
NTT DOCOMO, INC. |
| R1-2401158 |
Discussion on Waveform Characteristics of External Carrier Wave in Ambient IoT |
Indian Institute of Tech (M), IIT Kanpur |
| R1-2401184 |
Carrier-wave design for Ambient IoT |
InterDigital, Inc. |
| R1-2401261 |
Discussion on waveform characteristics of carrier-wave provided externally to the Ambient IoT device |
Google |
| R1-2401278 |
Discussion on Waveform characteristics of carrier-wave provided externally to the Ambient IoT device |
CEWiT |
| R1-2401311 |
On carrier-wave waveform characteristics for A-IoT |
MediaTek Inc. |
| R1-2401331 |
Consideration points on carrier-wave transmission for Ambient IoT |
LG Electronics |
| R1-2401448 |
Waveform characteristics of carrier-wave provided externally to the Ambient IoT device |
Qualcomm Incorporated |
| R1-2401481 |
Considerations for Waveform characteristics of carrier-wave |
Samsung |
| R1-2401695 |
FL summary#1 on CW waveform characteristics for A-IoT |
Moderator (Spreadtrum Communications) |
| R1-2401788 |
FL summary#2 on CW waveform characteristics for A-IoT |
Moderator (Spreadtrum Communications) |
| R1-2401855 |
Final summary on CW waveform characteristics for A-IoT |
Moderator (Spreadtrum Communications) |
| 9.5 |
Enhancements of network energy savings for NR (Netw_Energy_NR_enh) |
|
| R1-2401143 |
Workplan for Rel-19 network energy savings WI |
Rapporteurs (Ericsson, Apple) |
| 9.5.1 |
On-demand SSB SCell operation |
|
| R1-2400062 |
Discussion on on-demand SSB SCell operation |
Spreadtrum Communications |
| R1-2400097 |
Discussion of on-demand SSB Scell operation |
FUTUREWEI |
| R1-2400119 |
On-demand SSB SCell operation for NES |
Huawei, HiSilicon |
| R1-2400176 |
On-demand SSB SCell operation |
Ericsson |
| R1-2400180 |
On-demand SSB Scell Operation |
Nokia, Nokia Shanghai Bell |
| R1-2400208 |
Discussion on On-Demand SSB SCell operation |
Transsion Holdings |
| R1-2400250 |
Discussions on on-demand SSB Scell operation |
vivo |
| R1-2400335 |
Discussion on on-demand SSB SCell operation |
CMCC |
| R1-2400369 |
Design of on-demand SSB SCell operation |
Intel Corporation |
| R1-2400399 |
On-demand SSB SCell Operation |
Google |
| R1-2400441 |
Discussion on on-demand SSB SCell operation |
CATT |
| R1-2400492 |
Discussion on on-demand SSB for NES |
ZTE, Sanechips |
| R1-2400515 |
On-demand SSB delivery of NES cells |
Dell Technologies |
| R1-2400525 |
Discussion on on-demand SSB SCell operation |
Honor |
| R1-2400566 |
Discussion on on-demand SSB SCell operation |
xiaomi |
| R1-2400599 |
Discussion on the enhancement to support on demand SSB SCell operation |
OPPO |
| R1-2400667 |
Discussion on on-demand SSB operation for SCell |
China Telecom |
| R1-2400740 |
On-demand SSB SCell operation |
Samsung |
| R1-2400806 |
Discussion on on-demand SSB for SCell operation |
NEC |
| R1-2400821 |
Discussion on On-demand SSB SCell operation |
InterDigital, Inc. |
| R1-2400901 |
Discussion on on-demand SSB SCell operation |
Panasonic |
| R1-2400927 |
On-demand SSB SCell operation for NES |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2401020 |
On-demand SSB SCell operation |
Apple |
| R1-2401053 |
Discussion on on-demand SSB SCell operation |
NTPU |
| R1-2401085 |
On-demand SSB SCell operation |
Lenovo |
| R1-2401123 |
Discussion on on-demand SSB SCell operation |
NTT DOCOMO, INC. |
| R1-2401190 |
Discussion on On-demand SSB SCell operation |
ITRI |
| R1-2401196 |
On-demand SSB for SCell |
ASUSTeK |
| R1-2401206 |
Discussion on on-demand SSB SCell operation |
Fujitsu |
| R1-2401212 |
Discussion of on-demand SSB SCell operation |
CAICT |
| R1-2401232 |
Discussion on On-demand SSB SCell operation |
ETRI |
| R1-2401279 |
Discussion on on-demand SSB Scell operation |
CEWiT |
| R1-2401291 |
On-demand SSB SCell operation |
MediaTek Inc. |
| R1-2401332 |
On-demand SSB SCell operation |
LG Electronics |
| R1-2401449 |
On-demand SSB operation for Scell |
Qualcomm Incorporated |
| R1-2401473 |
Discussion on on-demand SSB SCell operation |
NTPU |
| R1-2401673 |
Summary #1 of on-demand SSB for NES |
Moderator (LG Electronics) |
| R1-2401674 |
Summary #2 of on-demand SSB for NES |
Moderator (LG Electronics) |
| R1-2401675 |
Summary #3 of on-demand SSB for NES |
Moderator (LG Electronics) |
| R1-2401840 |
Summary #4 of on-demand SSB for NES |
Moderator (LG Electronics) |
| 9.5.2 |
On-demand SIB1 for idle/inactive mode UEs |
|
| R1-2400063 |
Discussion on on-demand SIB1 for idle/inactive mode UEs |
Spreadtrum Communications |
| R1-2400098 |
Discussion of on-demand SIB1 for idle/inactive mode UEs |
FUTUREWEI |
| R1-2400120 |
Discussion on on-demand SIB1 for NES |
Huawei, HiSilicon |
| R1-2400181 |
On-demand SIB1 for Idle/Inactive mode UEs |
Nokia, Nokia Shanghai Bell |
| R1-2400209 |
Discussion on on-demand SIB1 transmission |
Transsion Holdings |
| R1-2400251 |
Discussions on on-demand SIB1 for idle/inactive mode UEs |
vivo |
| R1-2400336 |
Discussion on-demand SIB1 for UEs in idle/inactive mode |
CMCC |
| R1-2400370 |
Study of on-demand SIB1 for idle/inactive mode UEs |
Intel Corporation |
| R1-2400400 |
On-demand SIB1 for Idle/Inactive Mode UE |
Google |
| R1-2400442 |
Discussion on on-demand SIB1 |
CATT |
| R1-2400493 |
Discussion on on-demand SIB1 for UEs in idle or inactive mode |
ZTE, Sanechips |
| R1-2400567 |
Discussion on on-demand SIB1 for idle/inactive mode UEs |
xiaomi |
| R1-2400600 |
Discussion on the enhancement to support on demand SIB1 for idle/inactive mode UE |
OPPO |
| R1-2400668 |
Discussion on on-demand SIB1 for idle/inactive mode UEs |
China Telecom |
| R1-2400741 |
On-demand SIB1 for idle/inactive mode UEs |
Samsung |
| R1-2400807 |
Discussion on on-demand SIB1 for UEs in idle/inactive mode |
NEC |
| R1-2400822 |
Discussion on On-demand SIB1 for idle/inactive mode UEs |
InterDigital, Inc. |
| R1-2400861 |
Considerations on on-demand SIB1 for idle/inactive mode UEs |
Sony |
| R1-2400902 |
Discussion on on-demand SIB1 for idle/inactive mode UEs |
Panasonic |
| R1-2400928 |
On-demand SIB1 for NES |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2401021 |
On On-demand SIB1 for IDLE/INACTIVE mode UEs |
Apple |
| R1-2401054 |
Scope of on-demand SIB study |
NTPU |
| R1-2401086 |
On-demand SIB1 for idle/inactive mode UEs |
Lenovo |
| R1-2401124 |
Discussion on on-demand SIB1 for idle/inactive mode UEs |
NTT DOCOMO, INC. |
| R1-2401144 |
Study of on-demand SIB1 for UEs in idle/inactive mode for NES |
Ericsson |
| R1-2401176 |
Discussion on on-demand SIB1 transmission for idle UEs |
Sharp |
| R1-2401197 |
Triggering of on-demand SIB1 |
ASUSTeK |
| R1-2401204 |
Discussion on on-demand SIB1 transmission for network energy savings |
Fujitsu |
| R1-2401233 |
Discussion on on-demand SIB1 for idle/inactive mode UEs |
ETRI |
| R1-2401253 |
Views on On-demand SIB1 operation for idle/inactive UEs |
Vodafone |
| R1-2401280 |
Discussion on on-demand SIB1 |
CEWiT |
| R1-2401292 |
On-demand SIB1 for idle or inactive mode UEs |
MediaTek Inc. |
| R1-2401333 |
On-demand SIB1 for idle/inactive mode UEs |
LG Electronics |
| R1-2401450 |
On-demand SIB1 procedure |
Qualcomm Incorporated |
| R1-2401474 |
Scope of on-demand SIB study |
NTPU |
| R1-2401536 |
Discussions on on-demand SIB1 for idle/inactive mode UEs |
vivo |
| R1-2401565 |
Discussions on on-demand SIB1 for idle/inactive mode UEs |
vivo |
| R1-2401661 |
FL summary 1 for on-demand SIB1 in idle/inactive mode |
Moderator (MediaTek) |
| R1-2401662 |
FL summary 2 for on-demand SIB1 in idle/inactive mode |
Moderator (MediaTek) |
| R1-2401663 |
FL summary 3 for on-demand SIB1 in idle/inactive mode |
Moderator (MediaTek) |
| 9.5.3 |
Adaptation of common signal/channel transmissions |
|
| R1-2400064 |
Discussion on adaptation of common signal/channel transmissions |
Spreadtrum Communications |
| R1-2400099 |
Discussion of the adaptation of common signal/channel transmissions |
FUTUREWEI |
| R1-2400121 |
Adaptation of common signal/channel transmissions |
Huawei, HiSilicon |
| R1-2400182 |
Adaptation of common signal/channel transmissions |
Nokia, Nokia Shanghai Bell |
| R1-2400210 |
Discussion on adaptive transmission of common signal or common channel |
Transsion Holdings |
| R1-2400252 |
Discussions on adaptation of common signal/channel transmissions |
vivo |
| R1-2400337 |
Discussion on adaptation of common signal/channel transmissions |
CMCC |
| R1-2400371 |
Adaptation of common signal/channel transmissions for Network Energy Saving |
Intel Corporation |
| R1-2400401 |
Adaptation of Common Signals |
Google |
| R1-2400443 |
Discussion on adaptation of common signal/channel transmissions |
CATT |
| R1-2400494 |
Discussion on common signal_channel for NES |
ZTE, Sanechips |
| R1-2400526 |
Discussion on adaptation of common signal channel transmissions |
Honor |
| R1-2400568 |
Discussion on adaptation of common signal and channel transmissions |
xiaomi |
| R1-2400601 |
Discussion on adaptation of common signal/channel transmission |
OPPO |
| R1-2400669 |
Discussion on common signal/channel adaptation |
China Telecom |
| R1-2400742 |
Adaptation of common signal/channel transmissions |
Samsung |
| R1-2400808 |
Discussion on adaptation of common signal/channel transmissions for Cell DTX/DRX |
NEC |
| R1-2400823 |
Discussion on adaptation of common signal/channel transmissions |
InterDigital, Inc. |
| R1-2400862 |
Considerations on adaptation of SSB in time domain |
Sony |
| R1-2400903 |
Discussion on adaptation of common signal/channel transmission |
Panasonic |
| R1-2400929 |
Adaptation of Common Signals and Channels for NES |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2400979 |
Adaptation of common signals and channels |
Lenovo |
| R1-2401022 |
On adaptation of common signal/channel for NES enhancements |
Apple |
| R1-2401125 |
Discussion on adaptation of common signal/channel transmissions |
NTT DOCOMO, INC. |
| R1-2401145 |
Adaptation of common signal/channel transmissions for NES |
Ericsson |
| R1-2401149 |
Views on adaptation of SS/PBCH blocks |
KT Corp. |
| R1-2401177 |
Discussion on adaptation of common signal/channel transmissions |
Sharp |
| R1-2401205 |
Discussion on adaptation of common signal / channel transmissions |
Fujitsu |
| R1-2401234 |
Adaptation of common signal/channel transmissions |
ETRI |
| R1-2401281 |
Discussion on adaptation of common signal and channel transmissions |
CEWiT |
| R1-2401293 |
Adaptation of common signal/channel transmissions |
MediaTek Inc. |
| R1-2401334 |
Adaptation of common signal/channel transmissions |
LG Electronics |
| R1-2401451 |
Adaptation of common channel transmissions |
Qualcomm Incorporated |
| R1-2401728 |
Summary#1 of AI 9.5.3 for R19 NES |
Moderator (Ericsson) |
| R1-2401821 |
Summary#2 of AI 9.5.3 for R19 NES |
Moderator (Ericsson) |
| R1-2401856 |
Summary#3 of AI 9.5.3 for R19 NES |
Moderator (Ericsson) |
| R1-2401870 |
Final summary of AI 9.5.3 for R19 NES |
Moderator (Ericsson) |
| 9.6 |
Low-power wake-up signal and receiver for NR (NR_LPWUS) |
|
| R1-2400640 |
Work plan for Low-power wake-up signal and receiver for NR |
vivo, NTT DOCOMO |
| R1-2401871 |
Summary of RAN1 agreements on LP-WUS/WUR for NR |
Rapporteur (vivo) |
| 9.6.1 |
LP-WUS and LP-SS design |
|
| R1-2400065 |
Discussion on LP-WUS and LP-SS design |
Spreadtrum Communications |
| R1-2400093 |
Discussion on LP-WUS and LP-SS Design |
FUTUREWEI |
| R1-2400123 |
Signal Design of LP-WUS and LP-SS |
Huawei, HiSilicon |
| R1-2400211 |
Discussion on LP-WUS and LP-SS design |
Transsion Holdings |
| R1-2400253 |
Discussion on LP-WUS and LP-SS design |
vivo |
| R1-2400272 |
Discussion on LP-WUS and LP-SS Design |
TCL |
| R1-2400338 |
Discussion on LP-WUS and LP-SS design |
CMCC |
| R1-2400444 |
Design of LP-WUS and LP-SS |
CATT |
| R1-2400473 |
Discussion on LP-WUS and LP-SS design |
NEC |
| R1-2400495 |
Discussion on LP-WUS design |
ZTE, Sanechips |
| R1-2400527 |
Discussion on LP-WUS and LP-SS design |
Honor |
| R1-2400569 |
Discussion on LP-WUS and LP-SS design |
xiaomi |
| R1-2400590 |
Signal design for LP-WUS and LP-SS |
OPPO |
| R1-2400634 |
Discussion on LP-WUS and LP-SS design |
Sharp |
| R1-2400670 |
Discussion on LP-WUS/LPSS design |
China Telecom |
| R1-2400684 |
Discussion on LP-WUS and LP-SS design framework for Low power WUS |
InterDigital, Inc. |
| R1-2400743 |
LP-WUS and LP-SS design |
Samsung |
| R1-2400811 |
Discussion on LP-WUS and LP-SS Design |
EURECOM |
| R1-2400813 |
Discussion on LP-WUS and LP-SS design |
Everactive |
| R1-2400863 |
LP-WUS and LP-SS design |
Sony |
| R1-2400883 |
Discussion on LP-WUS and LP-SS design |
Lenovo |
| R1-2400904 |
Discussion on the LP-WUS and LP-SS design |
Panasonic |
| R1-2400962 |
LP-WUS and LP-SS design |
Nokia, Nokia Shanghai Bell |
| R1-2401023 |
LP-WUS and LP-SS design |
Apple |
| R1-2401126 |
Discussion on LP-WUS and LP-SS design |
NTT DOCOMO, INC. |
| R1-2401146 |
LP-WUS and LP-SS design |
Ericsson |
| R1-2401150 |
Views on LP-WUS and LP-SS design |
KT Corp. |
| R1-2401208 |
Discussion on LP-WUS and LP-SS design |
Fujitsu |
| R1-2401317 |
On LP-WUS and LP-SS design |
MediaTek Inc. |
| R1-2401335 |
Discussion on LP-WUS and LP-SS design |
LG Electronics |
| R1-2401349 |
On LP-WUS and LP-SS design |
Nordic Semiconductor ASA |
| R1-2401452 |
LP-WUS and LP-SS design |
Qualcomm Incorporated |
| R1-2401665 |
Summary of discussions on LP-WUS and LP-SS design |
Moderator (vivo) |
| R1-2401746 |
Summary#2 of discussions on LP-WUS and LP-SS design |
Moderator (vivo) |
| R1-2401837 |
Summary#3 of discussions on LP-WUS and LP-SS design |
Moderator (vivo) |
| R1-2401863 |
Final summary of discussions on LP-WUS and LP-SS design |
Moderator (vivo) |
| 9.6.2 |
LP-WUS operation in IDLE/INACTIVE modes |
|
| R1-2400066 |
Discussion on LP-WUS operation in IDLE/INACTIVE modes |
Spreadtrum Communications |
| R1-2400124 |
Procedures and functionalities of LP-WUS in IDLE/INACTIVE mode |
Huawei, HiSilicon |
| R1-2400254 |
Discussion on LP-WUS operation in IDLE/INACTIVE modes |
vivo |
| R1-2400273 |
Discussion on LP-WUS Operation in IDLE/INACTIVE state |
TCL |
| R1-2400339 |
Discussion on LP-WUS operation in IDLE/INACTIVE modes |
CMCC |
| R1-2400445 |
System design and procedure of LP-WUS operation for UE in IDLE/Inactive Modes |
CATT |
| R1-2400474 |
Discussion on LP-WUS operation in RRC IDLE/INACTIVE mode |
NEC |
| R1-2400496 |
Discussion on LP-WUS operation in IDLE/INACTIVE mode |
ZTE, Sanechips |
| R1-2400570 |
Discussion on LP-WUS operation in Idle/Inactive modes |
xiaomi |
| R1-2400591 |
Discussion on LP-WUS operation in RRC_IDLE/INACTIVE modes |
OPPO |
| R1-2400635 |
Discussion on LP-WUS operation in IDLE/INACTIVE modes |
Sharp |
| R1-2400671 |
Discussion on LP-WUS operation in IDLE/INACTIVE modes |
China Telecom |
| R1-2400685 |
Discussion on LP-WUS operation in IDLE/INACTIVE modes |
InterDigital, Inc. |
| R1-2400744 |
LP-WUS operation in IDLE/INACTIVE modes |
Samsung |
| R1-2400814 |
Discussion on LP-WUS operation in IDLE/INACTIVE modes |
Everactive |
| R1-2400864 |
LP-WUS operation in IDLE / INACTIVE modes |
Sony |
| R1-2400884 |
Discussion on LP-WUS operation in Idle/Inactive modes |
Lenovo |
| R1-2400905 |
Discussion on LP-WUS operation in IDLE/INACTIVE modes |
Panasonic |
| R1-2400963 |
LP-WUS operation in IDLE/INACTIVE mode |
Nokia, Nokia Shanghai Bell |
| R1-2401024 |
LP-WUS operation in IDLE/INACTIVE modes |
Apple |
| R1-2401127 |
Discussion on LP-WUS operation in IDLE/INACTIVE modes |
NTT DOCOMO, INC. |
| R1-2401147 |
LP-WUS operation in IDLE and INACTIVE modes |
Ericsson |
| R1-2401209 |
Discussion on LP-WUS operation in IDLE/INACTIVE mode |
Fujitsu |
| R1-2401235 |
Discussion on LP-WUS operation in RRC IDLE/INACTIVE modes |
ETRI |
| R1-2401318 |
On LP-WUS operation in IDLE/INACTIVE modes |
MediaTek Inc. |
| R1-2401336 |
Discussion on LP-WUS operation in IDLE/INACTIVE modes |
LG Electronics |
| R1-2401348 |
On LP-WUS operation in IDLE/Inactive |
Nordic Semiconductor ASA |
| R1-2401453 |
LP-WUR operation in idle and inactive modes |
Qualcomm Incorporated |
| R1-2401629 |
Summary #1 on LP-WUS operation in IDLE/INACTIVE mode |
Moderator (Apple) |
| R1-2401630 |
Summary #2 on LP-WUS operation in IDLE/INACTIVE mode |
Moderator (Apple) |
| R1-2401631 |
Summary #3 on LP-WUS operation in IDLE/INACTIVE mode |
Moderator (Apple) |
| R1-2401872 |
Summary #4 (final) on LP-WUS operation in IDLE/INACTIVE mode |
Moderator (Apple) |
| 9.6.3 |
LP-WUS operation in CONNECTED modes |
|
| R1-2400067 |
Discussion on LP-WUS operation in CONNECTED modes |
Spreadtrum Communications |
| R1-2400125 |
Procedures and functionalities of LP-WUS in CONNECTED mode |
Huawei, HiSilicon |
| R1-2400255 |
Discussion on LP-WUS operation in CONNECTED modes |
vivo |
| R1-2400304 |
Discussion on LP-WUS procedures in Connected mode |
TCL |
| R1-2400340 |
Discussion on LP-WUS operation in CONNECTED mode |
CMCC |
| R1-2400446 |
System design and procedure of LP-WUS operation for UE in CONNECTED Modes |
CATT |
| R1-2400475 |
Discussion on LP-WUS operation in RRC CONNECTED mode |
NEC |
| R1-2400497 |
Discussion on LP-WUS operation in CONNECTED mode |
ZTE, Sanechips |
| R1-2400571 |
Discussion on LP-WUS operation in Connected mode |
xiaomi |
| R1-2400592 |
Consideration on wake-up procedure in connected mode |
OPPO |
| R1-2400636 |
Discussion on LP-WUS operation in CONNECTED modes |
Sharp |
| R1-2400672 |
Discussion on LP-WUS operation in CONNECTED modes |
China Telecom |
| R1-2400686 |
Discussion on RRC CONNECTED mode LP-WUS monitoring |
InterDigital, Inc. |
| R1-2400745 |
LP-WUS operation in CONNECTED modes |
Samsung |
| R1-2400815 |
Discussion on LP-WUS operation in CONNECTED modes |
Everactive |
| R1-2400865 |
LP-WUS operation in CONNECTED mode |
Sony |
| R1-2400874 |
Discussion on LP-WUS operation in CONNECTED modes |
Lenovo |
| R1-2400906 |
Discussion on LP-WUS operation in CONNECTED mode |
Panasonic |
| R1-2400964 |
LP-WUS operation in CONNECTED mode |
Nokia, Nokia Shanghai Bell |
| R1-2401025 |
LP-WUS operation in CONNECTED modes |
Apple |
| R1-2401128 |
Discussion on LP-WUS operation in CONNECTED mode |
NTT DOCOMO, INC. |
| R1-2401148 |
LP-WUS operation in CONNECTED mode |
Ericsson |
| R1-2401236 |
Discussion on LP-WUS operation in CONNECTED modes |
ETRI |
| R1-2401319 |
On LP-WUS operation in CONNECTED modes |
MediaTek Inc. |
| R1-2401337 |
Discussion on LP-WUS operation in CONNECTED modes |
LG Electronics |
| R1-2401454 |
LP-WUR operation in connected mode |
Qualcomm Incorporated |
| R1-2401698 |
FL summary #1 on LP-WUS operation in CONNECTED mode |
Moderator (NTT DOCOMO) |
| R1-2401836 |
FL summary #2 on LP-WUS operation in CONNECTED mode |
Moderator (NTT DOCOMO) |
| R1-2401862 |
FL summary #3 on LP-WUS operation in CONNECTED mode |
Moderator (NTT DOCOMO) |
| 9.7 |
Study on channel modelling for Integrated Sensing And Communication (ISAC) for NR (FS_Sensing_NR) |
|
| R1-2400574 |
Proposed work plan on channel modelling for ISAC |
xiaomi, AT&T |
| R1-2400575 |
Discussion on CR to introduce channel model for ISAC |
xiaomi, AT&T |
| R1-2401768 |
Session notes for 9.7 (Study on channel modelling for Integrated Sensing And Communication for NR) |
Ad-Hoc Chair (Huawei) |
| 9.7.1 |
ISAC deployment scenarios |
|
| R1-2400068 |
Discussion on ISAC deployment scenarios |
Spreadtrum Communications |
| R1-2400126 |
Deployment scenarios for ISAC channel model |
Huawei, HiSilicon |
| R1-2400155 |
Discussion for ISAC deployment scenarios |
New H3C Technologies Co., Ltd. |
| R1-2400167 |
Overview of ISAC Deployment Scenarios |
Tiami Networks |
| R1-2400174 |
Measurement data for ISAC deployment scenarios |
NIST |
| R1-2400256 |
Views on Rel-19 ISAC deployment scenarios |
vivo |
| R1-2400341 |
Discussion on ISAC deployment scenarios |
CMCC |
| R1-2400447 |
Discussion on ISAC deployment scenarios |
CATT |
| R1-2400504 |
Deployment scenarios for ISAC channel modeling |
Intel Corporation |
| R1-2400529 |
Discussion on ISAC Deployment Scenarios |
Ericsson |
| R1-2400572 |
Deployment scenarios and evaluation assumptions for ISAC channel model |
xiaomi |
| R1-2400616 |
Discussion on ISAC deployment scenarios |
OPPO |
| R1-2400644 |
ISAC Deployment Scenarios |
Sharp |
| R1-2400648 |
Discussion on ISAC deployment scenarios |
Nokia, Nokia Shanghai Bell |
| R1-2400652 |
Proposals for Integrated Sensing And Communication (ISAC) Deployment Scenarios |
NTPU |
| R1-2400673 |
Discussion on ISAC deployment scenarios |
China Telecom |
| R1-2400690 |
Deployment scenarios for integrated sensing and communication with NR |
NVIDIA |
| R1-2400746 |
Discussion on ISAC deployment scenarios |
Samsung |
| R1-2400759 |
Discussion on deployment scenarios for Integrated Sensing and Communication |
CICTCI |
| R1-2400791 |
Discussion on ISAC deployment scenarios |
LG Electronics |
| R1-2400801 |
Discussion on ISAC Deployment Scenarios |
Lekha Wireless Solutions |
| R1-2400866 |
Considerations on ISAC Deployment Scenario |
Sony |
| R1-2400881 |
Discussion on ISAC deployment scenarios and requirements |
EURECOM |
| R1-2400898 |
Considerations on ISCA deployment scenarios |
CAICT |
| R1-2400931 |
Discussion on ISAC deployment scenarios |
TOYOTA InfoTechnology Center |
| R1-2400935 |
Discussions on ISAC deployment scenarios |
Ruijie Network Co. Ltd |
| R1-2400953 |
FL summary on ISAC deployment scenarios |
Moderator (AT&T) |
| R1-2400960 |
ISAC Deployment Scenarios |
Panasonic |
| R1-2401026 |
Discussion on ISAC deployment scenarios |
Apple |
| R1-2401040 |
Discussion on ISAC deployment scenarios |
InterDigital, Inc. |
| R1-2401063 |
Discussion on ISAC deployment scenarios |
ZTE Corporation |
| R1-2401178 |
Discussion on ISAC deployment scenarios |
ITL |
| R1-2401220 |
Discussion on ISAC deployment scenarios |
Lenovo |
| R1-2401340 |
Discussions on ISAC deployment scenarios |
IIT Kanpur |
| R1-2401346 |
Deployment scenarios for ISAC |
Continental Automotive |
| R1-2401355 |
Views on Deployment Scenarios for ISAC for NR |
AT&T, FirstNet |
| R1-2401455 |
Discussion on ISAC deployment scenarios |
Qualcomm Incorporated |
| R1-2401466 |
Discussion on ISAC deployment scenario |
MediaTek |
| R1-2401468 |
Overview of ISAC Deployment Scenarios |
Tiami Networks |
| R1-2401705 |
FL summary #2 on ISAC deployment scenarios |
Moderator (AT&T) |
| 9.7.2 |
ISAC channel modelling |
|
| R1-2400069 |
Discussion on ISAC channel modeling |
Spreadtrum Communications |
| R1-2400127 |
Channel modeling methodology for ISAC |
Huawei, HiSilicon |
| R1-2400168 |
ISAC Channel Modeling Considerations |
Tiami Networks |
| R1-2400173 |
ISAC channel measurements and results for shared clusters |
BUPT, CMCC |
| R1-2400175 |
Power Calibration for Radar Cross Section (RCS) Measurement |
NIST |
| R1-2400257 |
Views on Rel-19 ISAC channel modeling |
vivo |
| R1-2400342 |
Discussion on channel modeling methodolgy for ISAC |
CMCC, BUPT, SEU, PML |
| R1-2400448 |
Discussion on ISAC channel modelling |
CATT |
| R1-2400505 |
Discussion on ISAC channel modeling |
Intel Corporation |
| R1-2400530 |
Discussion on ISAC Channel Modelling |
Ericsson |
| R1-2400573 |
Discussion on ISAC channel model |
xiaomi, BUPT |
| R1-2400617 |
Study on ISAC channel modelling |
OPPO |
| R1-2400645 |
ISAC Channel modelling |
Sharp |
| R1-2400649 |
Discussion on ISAC channel modelling |
Nokia, Nokia Shanghai Bell |
| R1-2400691 |
Channel modeling for integrated sensing and communication with NR |
NVIDIA |
| R1-2400747 |
Discussion on ISAC channel modelling |
Samsung |
| R1-2400760 |
Discussion on channel modelling for Integrated Sensing and Communication |
CICTCI |
| R1-2400792 |
Discussion on ISAC channel modelling |
LG Electronics |
| R1-2400810 |
Options for ISAC Channel Modelling |
Keysight Technologies UK Ltd |
| R1-2400818 |
Discussion on Channel Modelling for ISAC |
Lenovo |
| R1-2400841 |
Discussion on channel modelling for Integrated Sensing and Communication (ISAC) |
Southeast University |
| R1-2400867 |
Considerations on ISAC Channel Model |
Sony |
| R1-2400882 |
Discussion on ISAC channel modeling |
EURECOM |
| R1-2400899 |
Considerations on ISAC channel modelling |
CAICT |
| R1-2400932 |
Discussion on ISAC channel modelling |
TOYOTA InfoTechnology Center |
| R1-2400961 |
ISAC Channel Modelling |
Panasonic |
| R1-2401027 |
Discussion on ISAC channel modelling |
Apple |
| R1-2401041 |
Discussion on ISAC channel modeling |
InterDigital, Inc. |
| R1-2401064 |
Discussion on channel modelling for ISAC |
ZTE Corporation, BJTU |
| R1-2401347 |
Channel modelling for ISAC |
Continental Automotive |
| R1-2401356 |
Views on ISAC Channel Modelling |
AT&T |
| R1-2401456 |
Discussion on ISAC channel modelling |
Qualcomm Incorporated |
| R1-2401467 |
Discussion on ISAC channel modelling |
MediaTek |
| R1-2401494 |
Summary #1 on ISAC channel modeling |
Moderator (xiaomi) |
| R1-2401495 |
Summary #2 on ISAC channel modeling |
Moderator (xiaomi) |
| R1-2401496 |
Summary #3 on ISAC channel modeling |
Moderator (xiaomi) |
| 9.10 |
XR (eXtended Reality) for NR Phase 3 (NR_XR_Ph3) |
|
| R1-2400922 |
Work Plan for Rel-19 on XR (eXtended Reality) for NR Phase 3 |
Nokia, Qualcomm (Rapporteurs) |
| 9.10.1 |
Enabling TX/RX for XR during RRM measurements |
|
| R1-2400070 |
Discussion on enabling TX/RX for XR during RRM measurements |
Spreadtrum Communications |
| R1-2400129 |
Discussions on scheduling enhancements considering RRM measurements for XR |
Huawei, HiSilicon |
| R1-2400258 |
Discussion on enabling data transmissions for XR during RRM measurements |
vivo |
| R1-2400343 |
Discussion on enabling TX/RX for XR during RRM measurements |
CMCC |
| R1-2400360 |
Enabling TX/RX for XR during RRM measurements |
TCL |
| R1-2400423 |
Signaling control of scheduling restriction during measurement gap in support of XR services |
CATT |
| R1-2400476 |
Discussion on enabling TX/RX for XR during RRM measurements |
NEC |
| R1-2400498 |
Discussion on measurement gap for XR |
ZTE, Sanechips |
| R1-2400548 |
Discussion on enabling TX/RX for XR during RRM measurements |
xiaomi |
| R1-2400615 |
Enhancements to enable TX/RX for XR during RRM measurements |
OPPO |
| R1-2400677 |
RRM measurement gap and scheduling restriction enhancements for TX/RX of XR traffic |
Ericsson |
| R1-2400748 |
Discussion on enabling TX/RX for XR during RRM measurements |
Samsung |
| R1-2400820 |
Discussion on Enabling TX/RX for XR during RRM measurements |
InterDigital, Inc. |
| R1-2400836 |
Enabling TX/RX for XR during RRM measurements |
Lenovo |
| R1-2400868 |
Considerations on enabling UE Tx/Rx during RRM measurements |
Sony |
| R1-2400886 |
Enhancements to enable TX/RX for XR during RRM measurements |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2400889 |
Discussion on enabling TX/RX for XR during RRM measurements |
Panasonic |
| R1-2400921 |
Enabling TX/RX for XR during RRM measurements |
Nokia, Nokia Shanghai Bell |
| R1-2401028 |
Discussion on enabling TX/RX for XR during RRM measurements |
Apple |
| R1-2401033 |
Discussion on Enabling TX/RX for XR During RRM Measurements |
Meta |
| R1-2401129 |
Discussion on Enabling TX/RX for XR during RRM |
NTT DOCOMO, INC. |
| R1-2401211 |
On enabling Tx/Rx for XR during RRM measurements |
Google Inc. |
| R1-2401315 |
Discussion on enabling TX/RX for XR during RRM measurements |
MediaTek Inc. |
| R1-2401338 |
Discussion on XR during RRM measurements |
LG Electronics |
| R1-2401457 |
Enabling Tx/Rx for XR during RRM measurements |
Qualcomm Incorporated |
| R1-2401717 |
Moderator summary #1 - Enabling TX/RX for XR during RRM measurements |
Moderator (Nokia) |
| R1-2401718 |
Moderator summary #2 - Enabling TX/RX for XR during RRM measurements |
Moderator (Nokia) |
| 9.11 |
Non-Terrestrial Networks (NTN) for NR Phase 3 and Internet of Things (IoT) Phase 3 (NR_NTN_Ph3/IoT_NTN_Ph3) |
|
| R1-2400843 |
Work plan for NR_NTN_Ph3 |
THALES |
| R1-2401298 |
Work Plan for Rel-19 IoT NTN |
MediaTek Inc. |
| R1-2401730 |
Work plan for NR_NTN_Ph3 |
THALES, CATT |
| R1-2401769 |
Session notes for 9.11 (Non-Terrestrial Networks for NR Phase 3 and Internet of Things Phase 3) |
Ad-Hoc Chair (Huawei) |
| 9.11.1 |
NR-NTN downlink coverage enhancement |
|
| R1-2400071 |
Discussion on NR-NTN downlink coverage enhancement |
Spreadtrum Communications |
| R1-2400132 |
Discussion on downlink coverage enhancements for NR NTN |
Huawei, HiSilicon |
| R1-2400259 |
Discussion on NR-NTN downlink coverage enhancement |
vivo |
| R1-2400303 |
Discussion on NR NTN Downlink coverage enhancements |
THALES |
| R1-2400344 |
Discussion on NR-NTN DL coverage enhancement |
CMCC |
| R1-2400355 |
Discussion on DL coverage enhancement for NR NTN |
ZTE |
| R1-2400402 |
Downlink Coverage Enhancement for NR NTN |
Google |
| R1-2400424 |
Discussion on downlink coverage enhancement for NR NTN |
CATT |
| R1-2400478 |
NR-NTN downlink coverage enhancement |
NEC |
| R1-2400499 |
NR-NTN downlink coverage enhancement |
Fraunhofer IIS, Fraunhofer HHI |
| R1-2400516 |
Seamless NTN downlink coverage for high-availability services |
Dell Technologies |
| R1-2400528 |
Discussion on NR-NTN downlink coverage enhancement |
Honor |
| R1-2400549 |
Discussion on NR-NTN downlink coverage enhancement |
xiaomi |
| R1-2400576 |
NR-NTN downlink coverage enhancement |
InterDigital, Inc. |
| R1-2400602 |
Discussion on NR-NTN downlink coverage enhancement |
OPPO |
| R1-2400749 |
Discussion on downlink coverage enhancement for NR-NTN |
Samsung |
| R1-2400787 |
Discussion on NR-NTN downlink coverage enhancement |
LG Electronics |
| R1-2400837 |
Discussion on downlink coverage enhancements for NR NTN |
CCU, NTPU |
| R1-2400871 |
NR-NTN Downlink Coverage Enhancement |
PANASONIC |
| R1-2400875 |
Discussion on downlink coverage enhancement for NR NTN |
Lenovo |
| R1-2400897 |
An operator view on Downlink Coverage Enhancements for FR2-NTN |
Eutelsat Group |
| R1-2400971 |
Downlink coverage enhancements for NR over NTN |
Nokia, Nokia Shanghai Bell |
| R1-2401029 |
Study on NR-NTN Downlink Coverage Enhancement |
Apple |
| R1-2401059 |
Beam groups/patterns for NR-NTN downlink coverage enhancement |
Sharp |
| R1-2401079 |
Discussion on DL coverage enhancements for NR-NTN |
NICT |
| R1-2401083 |
Discussion on downlink coverage enhancement for NR NTN |
Baicells, CMCC |
| R1-2401130 |
Discussion on DL coverage enhancement for NR-NTN |
NTT DOCOMO, INC. |
| R1-2401237 |
Discussion on NR-NTN downlink coverage enhancement |
ETRI |
| R1-2401282 |
Link Level Enhancements for DL Coverage of NR NTN |
CEWiT |
| R1-2401299 |
Discussion on NR-NTN downlink coverage enhancement |
MediaTek Inc. |
| R1-2401342 |
On NR-NTN downlink coverage enhancement |
Ericsson |
| R1-2401458 |
Downlink coverage enhancement for NR NTN |
Qualcomm Incorporated |
| R1-2401470 |
An operator view on Downlink Coverage Enhancements for FR2-NTN |
Eutelsat Group |
| R1-2401592 |
Discussion on downlink coverage enhancement for NR NTN |
Baicells |
| R1-2401843 |
FL Summary #1: NR-NTN downlink coverage enhancements |
Moderator (THALES) |
| R1-2401844 |
FL Summary #2: NR-NTN downlink coverage enhancements |
Moderator (THALES) |
| R1-2401845 |
FL Summary #3: NR-NTN downlink coverage enhancements |
Moderator (THALES) |
| 9.11.2 |
Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands |
|
| R1-2400072 |
Discussion on support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands |
Spreadtrum Communications |
| R1-2400133 |
Discussion on HD-FDD RedCap UEs and eRedCap UEs for FR1-NTN |
Huawei, HiSilicon |
| R1-2400260 |
Discussion on support of RedCap and eRedCap UEs with NR-NTN |
vivo |
| R1-2400345 |
Discussion on the collision issues of HD-FDD Redcap UE in FR1-NTN |
CMCC |
| R1-2400356 |
Discussion on support of RedCap/eRedCap UEs for NR NTN |
ZTE |
| R1-2400425 |
Discussion on the operation of RedCap and eRedCap UEs In NTN |
CATT |
| R1-2400550 |
Discussion on the support of Redcap UE for NTN operating on FR1 bands |
xiaomi |
| R1-2400603 |
Discussion on supporting of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands |
OPPO |
| R1-2400627 |
Discussion on half-duplex RedCap issues for NTN FR1 operation |
InterDigital, Inc. |
| R1-2400750 |
Discussion on support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands |
Samsung |
| R1-2400788 |
Discussion on support of (e)RedCap UEs with NR-NTN operating in FR1-NTN bands |
LG Electronics |
| R1-2400972 |
RedCap support for NR over NTN while operating in FR1-NTN bands |
Nokia, Nokia Shanghai Bell |
| R1-2401030 |
Discussion on support of RedCap UEs with NR NTN operation |
Apple |
| R1-2401131 |
Discussion on support of RedCap and eRedCap UEs in FR1-NTN |
NTT DOCOMO, INC. |
| R1-2401194 |
On HD-FDD Redcap UEs for NTN |
Ericsson |
| R1-2401238 |
Discussion on HD UEs with NR NTN |
ETRI |
| R1-2401300 |
Discussion on support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands |
MediaTek Inc. |
| R1-2401459 |
Support of Redcap and eRedcap UEs in NR NTN |
Qualcomm Incorporated |
| R1-2401847 |
Summary for Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands |
Moderator (CATT) |
| R1-2401861 |
Final summary for Support of RedCap and eRedCap UEs with NR NTN operating in FR1-NTN bands |
Moderator (CATT) |
| 9.11.3 |
NR-NTN uplink capacity/throughput enhancement |
|
| R1-2400073 |
Discussion on NR-NTN uplink capacity/throughput enhancement |
Spreadtrum Communications |
| R1-2400134 |
Discussion on uplink capacity/throughput enhancement for FR1-NTN |
Huawei, HiSilicon |
| R1-2400261 |
Discussion on NR-NTN uplink capacity enhancement |
vivo |
| R1-2400346 |
Discussion on the NR-NTN uplink capacity/throughput enhancements |
CMCC |
| R1-2400357 |
Discussion on UL capacity enhancement for NR NTN |
ZTE |
| R1-2400403 |
Uplink Capacity Enhancement for NR NTN |
Google |
| R1-2400426 |
Discussion on UL capacity enhancement for NR NTN |
CATT |
| R1-2400479 |
NR-NTN uplink capacity/throughput enhancement |
NEC |
| R1-2400517 |
Disaggregated NTN uplink and downlink sessions |
Dell Technologies |
| R1-2400551 |
Discussion on NR-NTN PUSCH capacity enhancement |
xiaomi |
| R1-2400604 |
Discussion on NR-NTN uplink capacity/throughput enhancement |
OPPO |
| R1-2400628 |
NR-NTN uplink capacity/throughput enhancement |
InterDigital, Inc. |
| R1-2400674 |
Discussion on NR-NTN uplink enhancement |
China Telecom |
| R1-2400751 |
Discussion on uplink capacity/throughput enhancement for NR-NTN |
Samsung |
| R1-2400789 |
Discussion on NR-NTN uplink capacity/throughput enhancement |
LG Electronics |
| R1-2400819 |
Discussion on NR-NTN Uplink Capacity/Throughput Enhancement |
Lenovo |
| R1-2400824 |
Uplink capacity/throughput enhancement for NR-NTN |
Panasonic |
| R1-2400973 |
On NR-NTN uplink capacity/throughput enhancements |
Nokia, Nokia Shanghai Bell |
| R1-2400977 |
On uplink capacity/throughput enhancement for NR NTN |
Ericsson |
| R1-2401031 |
Study on NR-NTN Uplink Capacity Enhancement |
Apple |
| R1-2401080 |
NR-NTN uplink capacity/throughput enhancement |
NICT |
| R1-2401132 |
Discussion on NR-NTN uplink capacity/throughput enhancement |
NTT DOCOMO, INC. |
| R1-2401133 |
NR-NTN uplink capacity/throughput enhancement |
Sharp |
| R1-2401239 |
Discussion on NR-NTN uplink capacity/throughput enhancement |
ETRI |
| R1-2401301 |
Discussion on NR-NTN uplink capacity and throughput |
MediaTek Inc. |
| R1-2401460 |
NR-NTN uplink capacity / throughput enhancement |
Qualcomm Incorporated |
| R1-2401484 |
Discussion on NR-NTN uplink capacity/throughput enhancement |
LG Electronics |
| R1-2401543 |
Feature lead summary #1 of AI 9.11.3 on NR-NTN uplink capacity and throughput |
Moderator (MediaTek) |
| R1-2401791 |
Feature lead summary #2 of AI 9.11.3 on NR-NTN uplink capacity and throughput |
Moderator (MediaTek) |
| 9.11.4 |
IoT-NTN uplink capacity/throughput enhancement |
|
| R1-2400074 |
Discussion on IoT-NTN uplink capacity/throughput enhancement |
Spreadtrum Communications |
| R1-2400135 |
Discussion on UL capacity enhancements for IoT NTN |
Huawei, HiSilicon |
| R1-2400262 |
Discussion on IoT-NTN uplink capacity enhancement |
vivo |
| R1-2400347 |
Discussion on the IoT -NTN uplink capacity/throughput enhancements |
CMCC |
| R1-2400358 |
Discussion on UL capacity enhancement for IoT NTN |
ZTE |
| R1-2400427 |
Discussion on UL capacity enhancement for IoT NTN |
CATT |
| R1-2400480 |
IoT-NTN uplink capacity/throughput enhancement |
NEC |
| R1-2400552 |
Discussion on IoT-NTN uplink capacity enhancement |
xiaomi |
| R1-2400605 |
Discussion on IoT-NTN uplink capacity/throughput enhancement |
OPPO |
| R1-2400629 |
IoT-NTN uplink capacity/throughput enhancement |
InterDigital, Inc. |
| R1-2400752 |
Discussion on uplink capacity/throughput enhancement for IoT-NTN |
Samsung |
| R1-2400790 |
Discussion on IoT-NTN uplink capacity/throughput enhancement |
LG Electronics |
| R1-2400876 |
Discussion on uplink capacity enhancement for IoT NTN |
Lenovo |
| R1-2400879 |
IoT-NTN uplink capacity enhancement |
Nokia, Nokia Shanghai Bell |
| R1-2401032 |
Discussion on IoT-NTN uplink capacity enhancement |
Apple |
| R1-2401061 |
IoT NTN uplink enhancement with NPRACH multiplexing |
Sharp |
| R1-2401195 |
On uplink capacity enhancements for IoT-NTN |
Ericsson |
| R1-2401240 |
Discussion on IoT-NTN uplink capacity enhancement |
ETRI |
| R1-2401302 |
Discussion on IoT-NTN uplink capacity and throughput |
MediaTek Inc. |
| R1-2401373 |
IoT-NTN uplink capacity-throughput enhancement |
Mavenir |
| R1-2401461 |
IOT-NTN uplink capacity/throughput enhancement |
Qualcomm Incorporated |
| R1-2401607 |
FL Summary #1 for IoT-NTN |
Moderator (Sony) |